i18n / l10n: Document the decision to accept only primary languages etc.

[fllp]

There are currently three project languages for German:
German (Germany), German (Austria) and German (de).
This is unnecessary and having only one tranlsation (German (de)) should be considered:

• for one, there is no such distinction in the official SFOS translations
• also, it is unclear which version will end up in Patchmanager:
  How does the App determine the locale variant to be used once installed?
• And: In the worst case, this 'split' triples efforts for updating or improving translations

[CODeRUS]

It's up to users to request languages for translation and translate it.
system language is used. My best guess it's a de_de one.

[fllp]

Would it not be reasonable to remove Austria and Germany then? As said, this clutters the translations.
And if I understand it correctly, there is no way to switch to those custom languages right now.

[nephros]

#52 should resolve this. Closing.

[Olf0]

Well, there are more to handle: #46 (comment)

[b100dian]

I've updated transifex with removal of ca, de_AT, de_DE, en_FI, it, ja.
I don't know yet how to handle e.g. moving fr_FR to fr (L.E: it's manual and might lose collaborators: https://docs.transifex.com/projects/adding-and-removing-project-languages/#changing-a-target-language ).

[Olf0]

I've updated transifex with removal of ca, de_AT, de_DE, en_FI, it, ja.

Thanks!

I don't know yet how to handle e.g. moving fr_FR to fr (L.E: it's manual and might lose collaborators: https://docs.transifex.com/projects/adding-and-removing-project-languages/#changing-a-target-language ).

Well, the guide you linked to (but the jump target does not seem to work) describes the manual process very well (including "Do's" and "Dont's").
Mind that the empty fr might have to be deleted first, before

• Copy fr_FR over to fr (with no strings, currently) and delete fr_FR.

These few steps also shall be applied to

• Move pt_BR to pt (which does not exist, currently).

Plus:

• Just use nl, delete nl_BE (both seem to be at the same level).
• Just use fi, delete fi-FI (which has less strings translated).
• Just use sl, delete sl_SL (both seem to be at the same level).

And:

Delete src/qml/settings-patchmanager.ts

If we do not clean up this mess, now that we seem to have understood it, it will continue to cause confusion and additional, unnecessary research and work (for us or others) in the future.

I believe for a project with only a few strings like Patchmanager, locale specific localisation is much too detailed:

• All these would have to be maintained, but translators are scarce.
• All these have to be handled technically, which is no issue as long as the automatisms work fine, but becomes one, when they do not.
• The likeliness of translations becoming stale rises a lot with locale specific translations.

So let us please create a rule, "Only top level language localisations for Patchmanager".
IMO, delimiting the set of target languages is really better here!