.mojohaus.org/extra-enforcer-rules/requireEncoding.html
>
>
>
> Hans
>
>
>
>
>
> *From:* Alexandre Gacon
> *Sent:* donderdag 11 augustus 2022 8:04
> *To:* Hans Yperman
> *Cc:* Jody Garnett ; geoserver-users <
> geoserver-users@lists.sourceforge.net>
>
04
To: Hans Yperman
Cc: Jody Garnett ; geoserver-users
Subject: Re: [Geoserver-users] Using weblate in replacement of transifex -
First feedbacks
Thank you Hans for pointing me at the natice2ascii tool but I would like to
have something more straightforward between github and the translation solu
BFB844A0FCA
> (bottom)
>
>
>
> Hans
>
>
>
> *From:* Jody Garnett
> *Sent:* dinsdag 9 augustus 2022 15:53
> *To:* Alexandre Gacon
> *Cc:* geoserver-users
> *Subject:* Re: [Geoserver-users] Using weblate in replacement of
> transifex - First feedbacks
>
Hi Jody,
I will subscribe to the devel list to extend the discussion there.
For the two different items for the same language, Weblate is complaining
about the Chinese language: for example in
https://github.com/geoserver/geoserver/tree/main/src/web/core/src/main/resources,
you have one file in I
/internationalization-enhancements1.html#GUID-9DCDB41C-A989-4220-8140-DBFB844A0FCA
(bottom)
Hans
From: Jody Garnett
Sent: dinsdag 9 augustus 2022 15:53
To: Alexandre Gacon
Cc: geoserver-users
Subject: Re: [Geoserver-users] Using weblate in replacement of transifex -
First feedbacks
Thanks for the experiment
Thanks for the experiment :)
You may want to chat about this on the geoserver-devel list as it is about
care and feeding of the codebase.
I did not understand "have two different items for the same language", do
you have an example you can link to?
Jody
On Mon, Aug 8, 2022 at 3:29 AM Alexandre
Hi all,
I am studying if we could migrate the translation tooling from Transifex to
Weblate. I have started this because with the current setup Transifex is
changing a lot of translations when I upload updates of the translation
source, making it difficult to do the synchronization between GitHub
