What do you mean by not used?
The new projects missing from some languages is fixed now.
5 Likes
In that specific example (Lock code cannot be more than %n characters), it is probably safe to assume %n is plural, right? No systems limiting Lock code to a maximum of 1 character? So you would get away with omitting the singular case.
(Also probably maxlen>2, so even languages that have a distinct plural form for two of something should be safe.)
But maybe you saw other cases where it would be an issue?
Thanks, I’ve completed translation all projects, but still see the 98% of completion. I’ve found the some projects has empty string to translate. As you can see in screenshot the appsupport-bridge-bt project has 29 empty strings (0 words). I think this is an issue why I don’t have 100% of completion in Belarusian language.
Also I’ve found empty strings in other projects: sailfish-components-contacts-qt5, sailfishsilica-qt5, jolla-clock, appsupport-bridge-bt
Should I leave these strings as empty? or there is some error in project’s translation files?
As the “soft” deadline is approaching, what will happen to translations that are “suggested” but not approved by the coordinator yet? Will be included to the release?
And what about translations marked as “need work”?
And what will happen when there are like 5 slightly different suggestions like i see in some of the German translations? (like here: Translate | apkd-plugin-mobiledata-qofono | German | Sailfish OS Localisation)
Pick one at random from them?
Or did the language coordinator decide which to pick?
1 Like
I’m afraid the only and best option is to get the coordinator to do his job. The second option is to apply for the function of coordinator for the desired language.
While waiting for an official answer, here’s what I did – I checked other languages that reached 100% (for ie. Spanish) where I saw that empty strings were just confirmed and saved – I did the same 
Although there’s difference – we have only appsupport-bridge-bt with empty strings, other files are OK.
1 Like
If the source string is empty and there is no comment explaining what should be done with it, then it should be left empty. That is, just submit an empty string. This is the case for example for the label strings in appsupport-bridge-bt. The AppSupport bluetooth settings are merged in main bluetooth settings page, and use some of the same labels. (Probably we should look if there is some better solution to organize the code so that these empty strings could be avoided. Or at least add a comment to them that they should be left empty)
Then there are strings that are only used to change the format of some things, like for example address display format in the contacts components. Here is an example from Finnish, where we usually put the zip code before the city.
All these should have a comment describing what they do, and can usually be left empty if the default works for your language.
3 Likes
Coordinator needs to accept the suggestions, those won’t get included otherwise.
The “needs work” ones will get included in the release, if I remember right. But need to check that.
1 Like
Hi everyone, if community languages like Catalan are 100% translated by the 26th (lets see), does that mean they will be available on SailfishOS in an update? Or is there a way to do a beta test? to check on a device if everything is working well, for example.
I also don’t understand why there are “languages” and “community languages” - what is the difference?
Thanks
IIUC “languages” are officially supported and “community languages” are in progress. Since Catalan is 100% translated I guess it can be “moved”. @Keto does that AFAIK.
2 Likes
@marcaugust Important to note is that ‘community translations’ are not included in Sailfish by default - Jolla provides the translation infrastructure, but you (or at least someone) has to build a package for it, even if it’s 100% translated. Looking at OpenRepos, it seems like the last time anyone built a package was quite a few years ago:
But as @filip.k said, it could make sense to include Catalan (and Belarusian) by default if it’s going to be kept up-to-date with every release. Not to mention there’s all of the Indian languages that are included by default but haven’t actually been updated in a decade.
2 Likes
Unfortunately, I’m not a programmer and I don’t have the slightest idea how to do this. If there’s a step-by-step guide and it’s simple, I can try (it’s never too late to learn things!) but I don’t even know where to start.
1 Like
There’s a guide on how to do it in the link below, but maybe @martonmiklos could create the RPM for you.
Of course, if Catalan is added to the list of officially supported languages, you don’t need to create any RPM files yourself. Hopefully @Keto can add it into the 5.1 release.
2 Likes
Yes, the “community” languages are the ones that are not included in default translations pack.
We’ll try to include those that are 100% translated (or very close) in the release.
And yes, it would be great if the languages not included by default would also be easily installable, but I think we need to rework the translations packaging and some other things a bit for that.
4 Likes
No need to include nl_BE (unless it’s explicitly labelled as ‘Flemish (dialect)’ or so, so that it’s clear that someone who wants Dutch should just pick Dutch), otherwise there’s guaranteed to be people complaining
Thanks for clarification. I’ve submitted an empty string for these translation, but I don’t understand why Belarusian language has 98% of translated, when I’ve translated everything. Is there mistake in calculating the percentage of translation?
Hello, I took on this task to complete the missing parts of the Turkish translation. Sorry for being a bit late.
What would you like me to do with this part? As far as I read in the thread, we should leave places like this empty. Is that correct?
2 Likes
yes, you read correctly.
2 Likes