Hi, Andrea refers to Java specification of property files https://docs.oracle.com/javase/6/docs/api/java/util/Properties.html
Property file editors know how to use the Unicode escapes. With standard text editors it is not so simple, but possible (Finnish word “määrä” must be written as m\u00e4\u00e4r\u00e4. I do appreciate translations and have myself translated the whole OpenJUMP GIS program into Finnish (and started to translate the Geoserver UI 8 years ago but stopped when I noticed that I did not understand well enough what the items in the UI are really doing). However, publishing half made translations from Transifex is not the right thing to do for my mind if there is not an easy way for the users to switch into English that is also the language used in the user manuals. In crowd sourced translation users may translate word by word without understanding the syntax and the result may be rather odd until enough many iteration rounds have been performed. With my school Swedish some translations in one file I was browsing through are överraskande https://www.transifex.com/GeoServer/geoserver/viewstrings/#sv/web_core/179561217 but maybe they are common IT Swedish. As long as Geoserver UI does not have language selector I think that the translation projects should have a responsible editor who can make pull request to GitHub when they think that the translation is good to go. -Jukka Rahkonen- Lähettäjä: Mats Elfström <mats.elfst...@giskraft.se> Lähetetty: perjantai 29. lokakuuta 2021 14.06 Vastaanottaja: Andrea Aime <andrea.a...@geosolutionsgroup.com> Kopio: GeoServer Mailing List List <geoserver-users@lists.sourceforge.net> Aihe: Re: [Geoserver-users] Geoserver 2.20.0, Encoding German Umlaut-Problems Hi! I am confused here. You wrote:"That would have broken all property file editors (ones that are aware of what a property file is)." I was merely responding to a request from you:"We'll need someone to checkout GeoServer, re-encode all translation files to UTF8, and make a PR." Which was what I was preparing to do, with Notepad++, and nobody protested. Apparently, the problem could be fixed in another way. * Some words on Transifex. I think Transifex is a very good tool for the localization of Open source software. It enables volunteers who are not primarily programmers to contribute to internationalization in a simple way. An updated term thesaurus ensures consistency and aids translators. It is easy to check and compare translations across languages and so on. * Geoserver on Transifex But as it appears, the Geoserver Transifex files have not been used for several years. This means that the properties files in the repository are severely out of sync, and would be hard to bring up to speed. The project called Geoserver has 60 resources which currently, to a varying degree is translated into 41 languages. That adds up to a lot of language files. But right now, there are 456 'live' language files in the repo for 14 supported languages, Another matter is the connection between Transifex resources and properties files. For instance, the language file ...geoserver\src\web\core\src\main\resources\GeoServerApplication_sv.properties corresponds to the swedish section of the web_core resource, and gets downloaded as for_use_geoserver_web_core_sv.properties. The other resources seem to have similar naming connections. So, downloading and updating the repository manually would mean an error prone process of file copying and renaming. The naming convention also causes duplicate file names. There are 22 GeoServerApplication_de.properties files, for instance. Some scripting will be necessary. The Geonetwork team has provided scripts to download and distribute language files, but translators should not have to be bothered with adding their work to the repo. This should be done by the release team, shortly before release. * Conclusion I think localization is important to spread Open source software. For instance, QGIS is available in over 40 languages. I think Transifex is a very useful tool, and it is sad that the work done there for Geoserver has been neglected and brought into disrepair. Regards, Mats.E Den tors 28 okt. 2021 kl 14:35 skrev Andrea Aime <andrea.a...@geosolutionsgroup.com<mailto:andrea.a...@geosolutionsgroup.com>>: On Thu, Oct 28, 2021 at 1:59 PM Mats Elfström <mats.elfst...@giskraft.se<mailto:mats.elfst...@giskraft.se>> wrote: Hi! I just built Geoserver SNAPSHOT from my GitHub clone and deployed it under Tomcat9 on my Ubuntu 20 server. I can confirm that Swedish characters are rendered correctly on the welcome page on Chrome set for Swedish, even though Notepad++ says that the source file is ANSI encoded. They must be ISO-8859-1 encoded (of which ASCII is a subset, I believe?), as per property file specification. The file date for this file is 2021-08-14. I had offered to change all properties files to UTF-8, but the suggested PR seems to have fixed the problem. That would have broken all property file editors (ones that are aware of what a property file is). But the Transifex issue remains: Are Transifex Geoserver team members aware that their work is not used? And that the current language files need to be maintained file by file in the repository? I had no idea. We have no line of communication with the "translation team", and no clue as to what's happening on Transifex. We'd be happy if someone of them wants to step up and start migrating translations again to GeoServer... that's pretty much all we can do (review incoming PRs). Cheers Andrea == GeoServer Professional Services from the experts! Visit http://bit.ly/gs-services-us for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions Group phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 333 8128928 https://www.geosolutionsgroup.com/ http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail -- [Lähettäjä poisti kuvan.] GisKraft, Geodatakonsult Mats Elfström, Marsvinsholms stationsväg 80, 271 93 Ystad, Sweden tel: +46 70 595 39 35 / www.giskraft.se<http://www.giskraft.se>
_______________________________________________ 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
