On Wed, Oct 20, 2021 at 8:40 PM Mats Elfström <mats.elfst...@giskraft.se> wrote:
> The mystery deepens. > I am a member of the Swedish Geoserver Transifex team, and honestly > thought the work done there was being used. Not that I have been very > diligent, but I planned to change that. > So how are the language files created and maintained? Manually - file by > file? > I have no idea, never been involved in the GUI internationalization effort. We used to get pull requests every now and then. The volunteer that bridged Transifex with GeoServer source code stopped sending them (or at least, I don't remember seeing recent ones). For reference, the "params-extractor" extension has been sitting in extension for over 6 months now (it graduated in 2.19.x) and only has English and Korean translation... The Korean files come from one of the last Transifex related PRs, back in 2017. > If so, inadvertent changes of the character encoding is just one of many > error possibilities. > As it seems, the code base and Transifex are out of sync for four years, > so I doubt that they can be successfully merged now. > My offer to fix the encoding stands, as well as my request for a list of > language file folders. > Each GUI module has its set of internationalization files. Running the following command on Linux provides a full list: find . -name "GeoServerApplication*.properties" | grep -v target | sort > /tmp/geoserver_i18n.properties I've attached the result to this mail (list is too long the mail body). Community modules can be considered optional, only a subset is packaged for nightly builds, but anything in core (root modules) or extensions is part of releases. 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
geoserver_i18n.properties
Description: Binary data
_______________________________________________ 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
