Oops, I apologize, I see now that your screenshot is a newsletter email. I missed the paywall message on my first pass through wrapping newsletter strings. It’s on my list of spots that should be made translatable, but I’m tied up with paid work this week.
[My open source contributions to Ghost are not paid. I don’t work for the Ghost Foundation.]
Hey! I recently submitted a change for the Slovenian translation. I got a few suggestions from the bot which I subsequently corrected. Now I’m getting a message that some checks were not successful. Should I do something to solve them or will it be ok?
Hey! I’m behind on reviewing translations, but browser tests are probably just the CI system acting finicky. The i18n tests look like they’re fine, so it’s probably ok and you’re just waiting on a human to have a look. :)
Not a problem, just making sure everything’s ok. Thanks!
Hi. I’ve been testing Ghost.org as an alternative to managed WP hosting, Webflow, etc. I mailed support@ghost.org about some missing content in the es locale, and I managed to download, translate and upload some parts of the Source theme.
For other content, not included in the theme but in newsletter.json, I was directed to GitHub. So I forked and translated that set of strings en > es.
Cathy was very supportive — thank you!—but I’m new to Ghost and GitHub, and I don’t know how to edit my initial committ or add corrections. Any help would be appreciated. 
Hey @peces !
You’re going to go back to Github, specifically here: Ghost/ghost/i18n/locales/es/newsletter.json at main · juanpeces/Ghost · GitHub (that’s your repo, not the Ghost repo)
Press “.” to open the web editor. (It might take a minute)
Make your changes.
Commit your changes: The github.dev web-based editor - GitHub Docs (Just do the commit part. Don’t make a new branch or a new PR.)
That’s it! You can go back to the PR to make sure the new changes are visible there. (Reload the page, of course.)
Hey translators! If you’ve been wondering why the newsletter CTA (call to action) wasn’t translated, along with the publication date, well yeah, me too.
Those changes got merged today, so you’ll find new strings available in newsletter.json. (As always, it’ll be about a week until those changes are in the release, and then you won’t see any improvement until about a week after your translations themselves get merged. So… feel free to get translations in and maybe it’ll all come out together!)
Now… do we have ANY strings left besides in themes? Or was that maybe the last of them?
Is private blog landing page translated yet @Cathy_Sarisky ?
Oh, I dunno! Probably not! But it’s got like five words on it… how hard can it be? (Famous last words…)
sorry @Cathy_Sarisky I am not sure to understand are you suggesting that I translate it ? If yes, I am not sure how to proceed !
The private login screen is part of theming so can be translated in the same way as other theme elements. To override the file in a theme you can copy the base private.hbs into your custom theme and from there change the text as you see fit, or switch it over to using {{t}} which will read translation strings from your theme’s language files.
Themes don’t have a core translation facility like the standalone apps (comments, portal, etc) do because the text is completely free-form per theme rather than known static text that core apps have.
Thanks @Kevin , I’d completely missed that private.hbs could be overridden by the theme! 
No worries, it’s a pretty niche use-case!
The override works similarly to error.hbs or error-404.hbs. One thing to note as far as translation goes is that any server-provided error messages that get displayed will still be in English as we don’t have a translation mechanism for those (unless my knowledge of that area is out of date, in which case I’ll be happy to be proven wrong!).
Pretty sure you’re right! 
We opted not to translate the error messages at the API level when I was chasing English text in Portal, but instead to rewrite the common errors in the Portal package.
Awesome, Cathy. Just what I needed. I just did that. Thank you dearly.
Hi John, I asked a question in the “Themes” section, about translate Themes. I translate “Casper” theme to pt-BR, and my goal is to translate all other themes that are available in TryGhost github. But, I could not make a full translation, because its not possible at now to translate options that are in “package.json” and used in .hbs files. Todo, need to make changes in Ghost code base. I think in two ways. 1) create “package_<<lng>>.json” which will load as theme package of current theme language. - I did this code, test and works. But, change the current locale will not not imply to reload current theme package. So I need to make changes to reload and reapply the current theme to these method work. I could do this. but I’m not sure if this is the preferable approach. 2) Add <<lng>> sections direct to “package.json”, as in [“JSON - Multi Language · SimpleLocalize”](https://json multilanguage), also need make changes in Ghost codebase. What you think that need to todo in GhostCode base to deal with these question?
I am not John, but have a look here:
tldr: the official themes will not be translated until a new translation engine is built into Ghost, so that it fits the rest of the codebase.
@Cathy_Sarisky already worked on a “proof of concept” and linked the PR in the thread. If you’re keen on translating the official themes, I’d look into adding this functionality first.
I check that message, and is good to see other members of community to work to deliver translations to themes. But, both links there, are incomplete and will not work. As show in docs, themes MUST have “pagination.hbs” and “navigation.hbs” and there the location tags to theme translation works.
I’m also create a GitHub Organization- Ghost OpenSource i18 Themes to concentrate community efforts to deliver i18 themes to Ghost.
