There is an action from today’s meeting to check in with you on translation.
I saw that Regina was asking about use of weblate.osgeo.org - and I am not sure we had a chance to check-in how your experiment went earlier in the year.
I will check again how to do it (didn’t work on it for month) but to me it was quite easy to setup if you remove the duplicates we have in Chinese (we have one file in utf and one in latin1 with unicode character) because Weblate wants only one file per language in the repo.
I didn’t really test the whole git integration with my branch to check if we don’t have the encoding problem we had with Transifex. I will try to do a test this week on my fork and review the integration strategy we can have.
I will share my thoughts with you to see how we can setup the integration directly with the GeoServer repo instead of my fork.
I spent some time doing some tests. As already explained, there is an issue with the Chinese language which is available in two files, weblate does not like it.
The integration between weblate and github seems to work quite well, at least manually. It is possible to set up more advanced and automatic integration: I have to dig a little bit in it.
My main concern is that translation addition or update uses full unicode character, even for accented character available in the target encoding, making it more difficult to translate with a text editor (see https://github.com/AlexGacon/geoserver/blob/weblate/src/extension/mapml/src/main/resources/GeoServerApplication_fr.properties for example). I will check with Regina if something can be done but perhaps it is a wrong/little problem. I would be happy to know what other people doing translations think of this.
Given the fact that it does not seem possible to have Weblate keeping accented characters compatible with our compatible, I suggest to consider this fact as “not an issue” and to continue to work on moving to weblate.
Next point on the topic : is it possible to remove one of the two chinese translations in the repo?