It depends on the language : if the language has some equivalent in ISO-8859-1, the character will be kept as this. If not, the characters will be U encoded.
So for Finnish, the characters are kept : https://github.com/AlexGacon/geoserver/blob/main/src/web/wms/src/main/resources/GeoServerApplication_fi.properties But for Turkish, you have a mix : https://github.com/AlexGacon/geoserver/blob/main/src/web/wms/src/main/resources/GeoServerApplication_tr.properties Alexandre Le mer. 26 janv. 2022 à 08:48, Rahkonen Jukka (MML) < jukka.rahko...@maanmittauslaitos.fi> a écrit : > Hi, > > > > I have not yet quite understood what the synchronizing process is supposed > to do with non-latin1 characters. Are they pushed through something like > native2ascii > https://docs.oracle.com/javase/7/docs/technotes/tools/solaris/native2ascii.html, > so that Finnish word “määrä” would become “m\u00e4\u00e4r\u00e4” so that > the file encoding can be ISO-8859-1? > > > > What is funny in my example is that “ä” actually belongs to ISO-8859-1 > https://www.w3schools.com/charsets/ref_html_8859.asp, it is number 228, > ä. However, it certainly does not show correctly in at least some Java > programs with some Java versions without making the \u00e4 conversion. > Therefore I do finally a bunch of search-replace operations with text > editor when I translate locally. > > > > -Jukka Rahkonen- > > > > > > *Lähettäjä:* Alexandre Gacon <alexandre.ga...@gmail.com> > *Lähetetty:* keskiviikko 26. tammikuuta 2022 6.54 > *Vastaanottaja:* geoserver-users <geoserver-users@lists.sourceforge.net> > *Aihe:* [Geoserver-users] New Transifex synchronisation method > > > > Hi all, > > > > After several weeks of work to try having a sync between GitHub and > Transifex using the built-in feature, it seems that the feature is totally > broken, at least for working with PROPERTIES files, since it cannot keep > the encoding information for the translated files, either when pulling them > from GitHub or when pushing them to GitHub. > > > > Since it is a lot of file to maintain, a manual method would probably mean > that at one moment, such a sync will be stopped. So I keep investigating > how to make this sync as smooth as possible. > > > > I just tried the official Go command line tool of Transifex ( > https://github.com/transifex/cli) which went out of Alpha last month. The > result seems ok : I manage to send updated PROPERTIES source to Transifex > from my laptop and to retrieve updated PROPERTIES language files from it, > without any encoding changes. > > > > I have several questions for the dev team: > > - Should I create a ticket for this change ? > > - Should I include the Go CLI of Transifex in the Git repo or only let > instructions on how to get it and configure it? > > - For the moment the CLI configuration file is in a .tx folder at the root > of the repo: I will try to move it to a subfolder of the build folder : is > it the right thing to do? > > - I will also add SH and BAT files to easily execute the sync operations. > > - Is it possible to add some automatic executions of the sync operations > somewhere in the CI/CD? At least the GIT->TRANSIFEX sync, somewhere in > Jenkins? > > > > -- > > Alexandre Gacon > -- Alexandre Gacon
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
