Apart from the theme translation functionality, a stopping missing feature is the translation of portal and email component. All those messages are hardcoded in js files not translatable by themes.
Any non English spoken ghost webmaster is not able to offer a proper ghost project in his language easily.
Seconding this! I have a couple of Ghost websites in French, where I use Portal (because it’s gorgeous, simple to use and built-in). Portal (and the emails) are the only things that are not in French. Would be great for my customers to have everything in French.
It lacks translation of a pair of files (but translations are there commented) where I was not able to instantiate the i18n object (I am not good enough at js) hopping the repository owners would take advantage of it. But sadly, it seems they are not very interesting on portal translation right now.
Hope the pull request could help you.
Regards
To ensure that your theme is fully translatable, two core templates must exist in your theme. Check the following templates exist: pagination.hbs - exists in content/themes/mytheme/partials, copy the template navigation.hbs - exists in content/themes/mytheme/partials, copy the template
This part of translation guide doest not work and also get 404 errors.
I always have to hardcode translations for every update to my theme. That’s not acceptable.
And that without considering the impossibility of translating the email templates, the subscription form, and the entire backend. That sucks!
And that without considering the impossibility of translating the email templates, the subscription form, and the entire backend. That sucks!