[Geoserver-users] Translation workflow improvement

Hi,

As far as I know in the Java property files the special characters must be written with Unicode strings like here https://github.com/openjump-gis/openjump/blob/main/src/language/jump_de.properties or here https://github.com/openjump-gis/openjump/blob/main/src/language/jump_fr.properties.

-Jukka Rahkonen-

···

Lähettäjä: Alexandre Gacon <alexandre.gacon@…84…>
Lähetetty: torstai 4. marraskuuta 2021 16.38
Vastaanottaja: geoserver-users geoserver-users@lists.sourceforge.net
Aihe: [Geoserver-users] Translation workflow improvement

Hi,

After the recent debate on the translation of GeoServer, I have spent some time setting up a small project to see how the transifex-github integration works.

First, I have created a fork of the GeoServer repo on my own GitHub account and created a new branch named test_transifex (https://github.com/AlexGacon/geoserver/tree/test_transifex).

Then, I have activated the transifex-github integration between my GitHub account and the GeoServer Transifex project (to be removed and replaced later if we continue this way).

I have also created a new project in Transifex to avoid polluting the existing work of people working on translation (https://www.transifex.com/GeoServer/geoservertestgithub/dashboard/).

I have initiated my project with the property file of web/wms (https://github.com/AlexGacon/geoserver/blob/test_transifex/src/web/wms/src/main/resources/GeoServerApplication.properties), with a manual upload.

The next step was to upload some existing translations from transifex in language not available in GitHub to check later the behavior of the integration in this case.

After activation of the integration for my transifex project:

  • The main property file is synchronized on Transifex with the content from GitHub

  • The languages available on GitHub are visible on Transifex with the translation from GitHub

  • The imported languages are still visible on Transifex

After manual sync from Transifex to GitHub, PRs were created in GitHub for each new language.

As a final test, I updated in Transifex the GitHub French translation (54% coverage) with the one available in Transifex (more than 85% coverage), by downloading the translation file and then uploading it in the new transifex project. After manual sync request, a PR is created in GitHub for the new language (https://github.com/AlexGacon/geoserver/pull/7) : the diff result is not very clear (some lines are marked as removed and added whereas the content is the same).

Is it normal that for some languages you have unicode encoded characters ? (for example in Russian).

The main drawback on the configuration side of transifex is to have to configure all the different property files we want to translate and then upload the translations we want to retrieve from Transifex.

Regards

Alexandre Gacon

Thank you Jukka for this explanation. I conclude that the files sent by Transifex to GitHub are fine for GeoServer.

Regards
Alexandre

···

Alexandre Gacon

We just looked some of this up:

  • for *.properties files it is iso8859-1 or something which supports a range of characters
  • new: for *.utf8.properties it is UTF8
  • for *.java it is utf8
  • for text and markdown and xml I am Les sure
···


Jody Garnett