These instructions are intended help anyone who is interested in demo'ing the Ghost i18n proof-of-concept (or PoC) that I am throwing together. This PoC is for both the admin panel as well as server-side notifications.
(PS: this is all pre the new Zelda UI changes)
- Clone Ghost from my fork on GitHub
- Switch over to the
i18n-poc
branch (git checkout i18n-poc
) - Run
npm install
to download all node-related dependencies. - Now follow the regular Ghost "developer install from git" instructions. https://github.com/TryGhost/Ghost#developer-install-from-git
- Once you are done with the those instructions, grunt dev` to start Ghost in development mode. Ghost will then be running at http://localhost:2368/ghost/
- Because this is just a proof of concept, the language files are inlcuded as part of the repo (in the real world, this would not be the case)
- Also because this is just a PoC... only a small subset of items have been translated:
- Main navigation in the admin panel
- Settings --> About page (also in the admin panel)
- Initial notifications when you first run the blog (the "Welcome to Ghost" and "Trying to send an email" ones)
- The "Welcome to Ghost" email
- To force another locale, open
/core/client/app/app.js
and change the array on line 18n to only have a single locale of your choice (currently the only ones avilable areen
andes
)
I think that the translation should be indipendent. If there's a bug in a translation we should be able to update it without updating Ghost too.
It might happen very frequently, due to wrong quotes and/or other signs, for example a string like
Carica l'immagine
in italian could break the JavaScript and block Ghost completely. In this case it's better to update the translated JSON and ask people to update their language packs instead of waiting for the next update of Ghost.