Re: [Geoserver-devel] Use OSGEO weblate as translation tool - Development consequences

So if we make the minimum Java 11 for the next release cycle we could use UTF9 for the property files; that sounds like a good idea. -- Jody Garnett On Mon, 15 Aug 2022 at 09:48, Rahkonen Jukka < jukka.rahko...@maanmittauslaitos.fi> wrote: > Hi, > > > > As a reminder the start of the mailing

[Geoserver-devel] GeoServer/GeoTools PMC Meeting at 18:30 CET / 9:30 PST tomorrow

Reminder that the next PMC meeting is scheduled for tomorrow, August 16, at 18:30 CET. Cheers, Torben ___ Geoserver-devel mailing

Re: [Geoserver-devel] Use OSGEO weblate as translation tool - Development consequences

Hi, As a reminder the start of the mailing list thread when we discussed about starting to translate with Transifex: https://www.mail-archive.com/geoserver-users@lists.sourceforge.net/msg35112.html. Title was "Translation workflow improvement" but all mails do not appear in one thread so best

Re: [Geoserver-devel] Use OSGEO weblate as translation tool - Development consequences

If you wish to choose weblate I am sure we can work with what it does On Mon, Aug 15, 2022 at 12:12 AM Alexandre Gacon wrote: > Hi Jody, > > I had a look at the git history for the UTF8 file: the file was created by > you by renaming the CN ISO file ( >

Re: [Geoserver-devel] Use OSGEO weblate as translation tool - Development consequences

Hi Jody, I had a look at the git history for the UTF8 file: the file was created by you by renaming the CN ISO file ( https://osgeo-org.atlassian.net/browse/GEOS-10282). If I understand the JIRA issue correctly, this was related to the encoding issue in the translation files (the same old story)