We have a slight problem, and evident by this bug report, we have a mix of languages and their localised variants -- this has meant the "main" language misses out for different areas of the world. In some cases, the localised version is incomplete and the one users will see, such as de_DE (German for Germany users) while the complete de (German) translation goes unused (except for users outside of Germany).
To address this, the translations will be re-organised, I'm not too entirely sure how Transifex will react, since this will be a manual task.
For affected languages, you may need to re-add yourself as contributors in the upcoming days.
When requesting new languages in future:
If it's new, please pick the main language first.
If one exists, and you see a need for a localised version (e.g. en_US and en_GB use different spellings), the language request will be accepted. You can also ask us to duplicate the translation in full (e.g. de â de_DE) to save having to re-translate everything for a few differences.
If there's any comments or concerns about this change, please let me know!
Providing you have signed up for Transifex, you just go to the German language page and join the "team" / start translating. This should add you as a contributor.
I'm guessing once this change happens, anyone still in the "German (Germany)" team may just get notified it's been deleted. (Just as a guess )
Thanks for pointing that out â this is the sort of thing that needs to be known before any are dropped. In this case, Portuguese languages should remain untouched, meaning Brazil users will see a more completed translation.
âEnglish (United States)â is the source translation, so it isnât listed for translating.
We could copy de to de_DE, however I fear efforts would be duplicated if both co-exist. Welcome will use de if de_DE is not present and Germany is home to German, so a de locale will work on German speaking computers that happen to be outside of Germany.
We should start utilising Transifexâs review function, so we can have translators verifying existing work.
Itâs a permissions thing, Iâll need to confer with @Wimpy with how we approach this (I also might not have permissions to change permissions, ironically:grin: )
Kind of, as de_DE is mostly incomplete and resulted in most German (Germany) users welcomed in mostly English in 17.04, I was thinking of dropping de_DE entirely, as de isnât tied to a specific locale.
For both of those, the country locale is near completion (es_ES, nl_NL) but the main language is not. Chances are, itâs the country locale that would be widely used (which posed problems when Germanâs de_DE was incomplete) and the main locale should be used for Dutch/Spanish outside of Spain/Netherlands in theory.
I would suggest perfecting the most complete locale (so es_ES, nl_NL) and if we decide to merge these country locales to its general language locale, less efforts would have been wasted (except we would exclude merging any locales that do have major differences)
The two wonât sync up. That would need to be a manual âdeveloperâ task as it would risk losing the 3 existing contributors for âHebrew (Israel)â - to them, it might look like we âdeletedâ their locale if we were to change it.
For new languages, weâd prefer to opt for the âgeneralâ locale so it reaches more audiences, however since Israel is the main language for Hebrew, we should be good to keep it as it is for now.
It is possible to copy the existing translations for âHebrew (Israel)â to âHebrewâ, but that would mean duplicating translation efforts, so itâs all good to co-translate along the other Hebrew translators.
)