Translation Details please

[MixColumns]

Hello,
since the translation is one of the WIP Points in the Project planning could you please specify more details and maybe a timeline?

Could you also add to https://github.com/astarub/campus_app/wiki/Translation if the german translation is formal (Sie) or informal (Du)? I think the Portuguese translation will also not be done as i have not seen any progress in about 1-2 years. Also "Other" is very unspecific and should be removed imo. Once a new translation is started it can be added again.

I would advocate to make the translation for german formal but it makes sense to let the user choose. This means we would have german formal and german informal as translation files.

Can you please specify the naming convention for such cases? Also which prefix codes are being used?

Imo we should use the ISO 639 language codes https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes
This would result in l10n_XX_yyy.arb where yyy is an addition like informal, formal, local slang, etc.

[domai-tb]

Actually, the translation feature is at the current state not used at all. The code contains a l10n setup and basic definitions under assets/l10n, but not any of them is used in release v2.2 and prior. So the current translation state is essentially boiler plate code. This current state was the result of the fact that most content (RUB News and Events) are loaded from an external page and must be translated in an automatic way to achieve full localization - what leads, due the technical limitations and costs, to an low prioritization.

However, the Campus App team got new members and as far as I remember, @Noirox1 want to implement the localization feature. So, all static text field will be replaced to use the l10n localization.

We should use the ISO 639 language codes https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes
This would result in l10n_XX_yyy.arb where yyy is an addition like informal, formal, local slang, etc.

I totally agree at this point. All .arp-files should be following this naming convention. The naming convention for the actually strings is not clear defined by anyone of the Campus App team, but should be consistent.

Deciding between formal and informal German should be implemented too, but as far as I can think, we did not use any string whose German translation would result in a difference.

As soon as there is any progress, the documentation will be updated.