Translation of regions

[Valdnet]

In Transifex there are no names of regions to be translated for the Nextcloud settings.

It can do as with the choice of language, for example.: __region_name__.

[MorrisJobke]

Makes sense 👍

[MorrisJobke]

This is all defined in the file resources/locales.json:

https://github.com/nextcloud/server/blob/8c73b13ac870b0a6b75b701f4f52463c198421a5/resources/locales.json

@nickvergessen @rullzer @ChristophWurst: Do you have a clever way to translate this?

[MorrisJobke]

I would just add a new attribute localizedName and then put in there the name in the related language.

[MorrisJobke]

But even better would be if it would be depending on the currently selected language. Maybe I can somehow extract the name there and then put it into the lib translation files.

[Valdnet]

@MorrisJobke why is it twice Polish? The Polish language has no dialects.

{ "code":"pl_PL", "name":"Polish (Poland)"},
{ "code":"pl", "name":"Polish"},

[MorrisJobke]

It's how locale works I guess. There are just per language and then per language and per country. I would keep that for now and open a separate ticket for this duplicate entry.

[Valdnet]

@MorrisJobke In NC version 20.0.6 there are still no translated region.

[szaimen]

Seems like this is still valid on NC21.0.2

[Valdnet]

@MorrisJobke @nickvergessen Until now, there are no translated regions in Nextcloud 22.1.1. I looked at the translations in Transifex and there are also no text strings to translate about the names of the regions in this file "locales.json".

[Valdnet]

Translated text strings of region names from the file "locales.json" should be in the l10n directory for "settings".

Here are the translated names of the regions:

@MorrisJobke @rakekniven How do I get region name text strings in Transifex for "settings-1"?

He can put the locales.php file in the settings/lib/locales directory with the contents of the text strings with the region names to be scanned by nextcloud-bot and added to Transifex.

An example of the locales.php file:

<?php
p($l->t('Afrikaans'));
p($l->t('Afrikaans (Namibia)'));
p($l->t('Afrikaans (South Africa)'));
p($l->t('Aghem'));
//...
?>

[nickvergessen]

Morris is not here anymore.

The problem is it might overload translators a lot if they have to do it to finish the settings.
Maybe instead we can put it into a new l10n dir "regions" or something a like

[Salvador1313]

Думаю вам виднее как лучше. пн, 30 авг. 2021 г., 09:38 Joas Schilling ***@***.***>:

…

Morris is not here anymore. The problem is it might overload translators a lot if they have to do it to finish the settings. Maybe instead we can put it into a new l10n dir "regions" or something a like — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#14822 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AVLIXAHAAPB6GLBYXY5G4KTT7MRNXANCNFSM4HAWOTFA> .

[Valdnet]

Morris is not here anymore.

I did not know 😮.
Who has taken over his duties now?

Maybe instead we can put it into a new l10n dir "regions" or something a like

A very good thought 😉.

[Valdnet]

I can prepare region name text strings in a php file because it takes some time and developers have other more important things to do. I just need help changing the code in the personal.info.php file to reference the new l10n location.

[nickvergessen]

Isn't this ticket about regions and not locales?

[Valdnet]

Isn't this ticket about regions and not locales?

Hmmm. It concerns supposedly regions. This is what the setting option is called, but the settings are more suited to the localization settings.

In general, text strings are taken from the locales.json. However, in commit #14853 the code has been changed, where names should be changed to a given language. Only the translated text strings in l10n are missing.

[Valdnet]

The Issue somehow stood still.
I can still do the translation, I just need help changing the code in the personal.info.php file to reference the new l10n location.