Thanks for your patience last week Andrea in researching what needed to be
done, and reviewing the subsequent pull request.

Mats you are correct that translation is important, while transifex is
useful / popular I recently received feedback
<https://github.com/metadata101/iso19139.ca.HNAP/pull/191> on another pull
request asking to consider https://weblate.org/en/ as an open alternative.

I now know enough about transifex to review any pull request made to
improve our process
<https://docs.geoserver.org/latest/en/developer/translation.html>.
--
Jody Garnett


On Fri, 29 Oct 2021 at 06:52, Andrea Aime <andrea.a...@geosolutionsgroup.com>
wrote:

> On Fri, Oct 29, 2021 at 1:05 PM Mats Elfström <mats.elfst...@giskraft.se>
> wrote:
>
>> 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.
>>
>
> During the last GeoServer PSC meeting Jody and I sat down and looked at
> the issue with some patience and time (one hour of investigation,
> unlike the 5 minutes we can afford when answering here on the list). Turns
> out Java property files should not be encoded as UTF-8, but as ISO-8859-1,
> by Java specification itself (see somewhere here in the javadoc
> https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/Properties.html
> ).
> So, the problem had to be addressed in a different way.
>
>
>> 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.
>>
>
> We barely have the personnel to do releases (as you can see by release
> dates regularly slipping by due to lack of volunteers).
> We won't be able to also take on this, period. Someone other than the
> current core developers must step up and do it.
> This presentation might give you some perspective on what we are talking
> about, when we say "busy": https://t.co/y69loP6RpJ
>
>
>> * 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.
>>
>
> The work was started and managed outside of the core dev team (thankfully,
> otherwise it would not have happened at all, see above).
> Unfortunately the volunteer that bridged the two worlds disappeared. We
> need a new one.
> Writing the scripts is going to be only one of the tasks this person is
> tasked with, another issue is being present on Transifex, and get
> a feeling of which translations (out of the many) can actually be
> contributed to the project
>
> 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-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

Reply via email to