Ahoy, it’s time for Sailfish OS 5.2 translations round and this time there is three new components and about 250 strings to translate. Quite a lot tweaking and polishing has been going on around the UI, and also some new features have been added, so there is quite a lot of new strings.
The UK English translations are not there yet, so you need to rely on the engineering English as a source for now.
Lets aim for Friday 26th of June to get as much done as possible.
Please try to check old terms used, to keep consistency: e.g. if unsure how to translate the word “device”, put the word in the Search box to see how it has been previously translated into your language.
The same goes for language style (e.g. how to address the user).
Feel free to keep improving any old translations, even between L10n rounds.
Finally, please notice if there is a comment on a string to e.g. keep the translation short or some other guidance (via the “Content instructions” meta-language).
If you have any questions, please post them under the Localisation category.
EDIT: Going to list what I notice about the Mastodon component instead of individual replies:
there appear to be a lot of duplicate or even triplicate strings across the separate .ts files
most of the “something changed strings” , e.g. “started following you” do not feature a “%1” for the “actor”. I imagine this could be a problem for some languages.
the term “Post” is used a lot. I guess this should be “Toot”.
sent you a notification → I guess should be “sent you a message”?? (As in a PM vs. an app notification.)
For German, there’s a couple of “accepted” tanslations for AppSupport, which are translated as “Android™-App-Unterstützung”.
I believe as AppSupport is a product (or even Trademark?), it’s supposed to remain untranslated/the same.
@nephros Yes, the “no, not all of the strings again” is definitely suitable since they are tripled or quadrupled. I tried to keep “post” for generics like settings pages and other parts where it is potentially combined with similar objects from other services. The action of Mastodon posting and resulting service specific post object I used the service native “toot”'s translation, but probably too seldom. Need to review the final set of strings in place so the context and proximity can be judged. Let us see what happens when the English strings are updated for these currently unresolved questions of parameters and types of this service integration.
Yes, ts-tools solves that problem of consistency of identical or similar strings over the sets. Independently of re-typing or accepting the same translation the question pops up anyway. So it does not cure the curiosity.
Thanks to @rob_kouw for doing the Dutch translations already! I’ve changed some minor things like ‘privémodus’ to ‘privacymodus’ to distinguish it better from the browser’s private mode, but great work all around!
It’s referring to the Google Play store. This is a microG initial setting, with the description “Allow Google Play compatibility services to sync device information.”
There was a bug in the sailfish-components-timezone strings generation, and all those string were missing already in 5.1. The already translated strings have been restored there and for most languages there is only one new string in the timezone data. The few new languages unfortunately now have a huge chunk of untranslated strings there.
We also got the emergency alert message data integrated, so there is ~30 new strings related to those in jolla-settings-system.
.
