I don’t know if this is the best place to say this, but I have a feeling it is.
I noticed in the mobile version of the subscription portal that the wording on the annual plan was out of place.
The word “économiser” is too long compared to “save”. A minus symbol should have been used. It takes up less space and is just as easy to understand.
We just had a similar problem with German. Much more than ‘save’ just doesn’t fit there. [You should have seen how bad the German was - it was even longer!] I’ll drop in a - instead.
I noticed that newsletter locales are not (yet) available, is that correct? I am willing to help, but where to start, ie. where to find the newsletter template with public text?
The newsletter is mostly what you send to your members, right? Are you asking for the “view in browser”-type text?
well I mean the fixed text in the newsletter, eg. “Keep reading” and “More like this…”
Were to find the newsletter template or the aforementioned text?
Despite having added Dutch (nl) locale for search.json ([#21339]) the search box is still not using the Dutch (nl) locale.
the locale seems to be set correctly
<script defer src="https://cdn.jsdelivr.net/ghost/sodo-search@~1.4/umd/sodo-search.min.js" data-key="6f0fa7408a451d0565ac7169e2" data-styles="https://cdn.jsdelivr.net/ghost/sodo-search@~1.4/umd/main.css" data-sodo-search="https://domain/" data-locale="nl" crossorigin="anonymous"></script>
It got merged five days ago, but must have just missed the quasi-weekly package build. Sorry - sometimes things get merged but the app (portal/search/comments) doesn’t get version bumped, so the release message is confusing. It’s coming!
Newsletter i18n is coming in the next Ghost release. Translators, newsletter.json is available in Github now, so feel free to hop in whenever you like!
A quick note on a few tricky bits:
"You are receiving this because you are a <strong>%%{status}%% subscriber</strong> to {site}.": "",
site = your site name
status = free/complimentary/paid/trialing.
The strings for free, complimentary, paid, and trialing are also in the file, so these strings work together.
Your translations should retain the {site} and %%{status}%% markup.
Dates will be translated. The {date} string will become your language’s method of showing dates, including articles if required. (So for French, 13 October 2024) becomes le 13 octobre 2024.) It should ‘just work’, but please holler if it isn’t.
Note to @bastien - I produced what’s at best mediocre French for testing purposes. Fixes would be much appreciated.
@Cathy_Sarisky Thanks, I’m willing to help, but as I’m not a developer and I don’t know how to use Github, I don’t know how to do it. Do you want me to give feedback here or should I go to Github to suggest improvements?
The best way would be to follow the directions in the first post on this thread. :)
@Cathy_Sarisky I did a lot of proofreading of all the French files, and I sent a pull request. I followed the instructions to make it as clean as possible, but when I was sending my pull request and reviewing the changes I’d made, I wanted to correct myself, so I went back into the editor and tried to synchronise the branch, and then things went wrong, conflicts were detected even though I’d only made two small changes, a merge editor opened, I tried to clean things up properly but it didn’t work in the end. So I had to submit my first revision and didn’t manage to make the small corrections I wanted to make to my first revision.
If you want to share those small revisions with me, I’ll help you get them made. (I can ‘make a suggestion’ for them and you can accept them.)
Thanks for the detailed once-over! 
I think I’ve finally managed to send a new pull request.
Please find updated Czech translation, 100% phrases are done.
I think not currently! Congrats, you found something (besides themes) that we missed! 
I also think the staff invite emails are not covered yet.
Where can I find the files to add translatation ?
See the video in the very first post for directions on adding translations.
None of the admin side of Ghost has been translated. The admin area is presently English-only. So the staff invites are also presently untranslated. We’re at a point where site visitors can see only their language (if you have a translatable theme and all strings exist in your language), but that’s not yet true for staff.
Hi there
How to fix this and translate the paywall notification into german? I could’t spot those terms below in the github files.
My suggestions would be:
“Upgrade to continue reading.”: “Jetzt upgraden um weiterzulesen”,
“Become a paid member of {{siteTitle}} to get access to all premium content”: “Jetzt Abo abschließen und weiterlesen”,
Help very much appreciated :-)
Thanks + kind regards,
Markus
See this recent post - in brief, you need to add a content-cta to your theme and translate it.
