Hi,
For the UTF-8 file for Chinese, the Transifex update does not apply to it
but only to the one in ISO-8859 encoding : could I remove them from the
source code?
I just gave another try to Transifex and I still have unwanted changes
(translations removed without asking it): it will give a lot of
On Tue, Aug 16, 2022 at 1:21 AM Jody Garnett wrote:
> "could use UTF9 for the property files"
>
You're at one bit ahead from the rest of us LOL
Cheers
Andrea
==
GeoServer Professional Services from the experts!
Visit http://bit.ly/gs-services-us for more information.
==
Ing. Andrea Aime
@ge
tool and automatic workflows are of course
> very valuable.
>
>
>
> -Jukka Rahkonen-
>
>
>
>
>
> *Lähettäjä:* Jody Garnett
> *Lähetetty:* maanantai 15. elokuuta 2022 17.10
> *Vastaanottaja:* Alexandre Gacon
> *Kopio:* GeoServer
> *Aihe:* Re: [Geoserver-devel] Us
tic workflows are of course very
valuable.
-Jukka Rahkonen-
Lähettäjä: Jody Garnett
Lähetetty: maanantai 15. elokuuta 2022 17.10
Vastaanottaja: Alexandre Gacon
Kopio: GeoServer
Aihe: Re: [Geoserver-devel] Use OSGEO weblate as translation tool - Development
consequences
If you wish to choose web
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 (
> https://osgeo-org.atlassian.net/browse/GEO
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) a
You may have to search back in the geoserver-devel history or bug tracker
for details. I assume we were provided utf8 translations and wished to
preserve them?
When using the UI in weblate can folks see the native characters regardless
of encoding used?
What I remember is that we needed UTF8 to s
I try to keep only the UTF-8 file as the source for Chinese, along with the
other languages in ISO-8859-1: the display of the file content in weblate
is totally broken. I have to define another fake component configured to
support UTF-8 encoding to be able to manage it correctly.
What is the reaso
Hi Jody,
You are guessing well: it is all about the Chinese language : for weblate
it is the same language defined twice so it cannot cope with it.
I have to check how weblate can work with having one of the languages in
UTF-8 whereas the other ones are in ISO-8859-1 : I fear that it will mean
to
Weblate is a good idea; we held back perviously because of lack of hosting.
However if OSGeo is able to host :)
I do not understand about two items for the same language: can you provide
links in the github repo? Do you mean two properties files; or two entries
in the same property file. Or two en
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
11 matches
Mail list logo
