[Geoserver-devel] Translations on transifex (from geoserver-user)

Like Andrea, I moved this post from the User-List to the Developer-List ...

Stefan, thank you for the fantastic work you did! I'm going to review
the geoserver 2.2.x translations and create a pull request afterwards.
Before I can create one, I like to test the encodings because for the
German properties files its changed (like Chris mentioned at
http://osgeo-org.1560.n6.nabble.com/Translations-was-Re-i18n-File-encoding-for-Java-properties-files-tp5009414p5009462.html)
to ISO-8859. Could anybody give me a hint to change the default
encoding from UTF-8 to ISO-8859 for such resources at build time. In
the root-pom of the src folder you can find this section for the maven
compiler and resource plugin:
<encoding>UTF-8</encoding>

I guess this would break the encoding for the German language
properties files...

At the moment there are 15 resource listed that can be potentially
translated by several translation teams (such as German)..

Chris and Oscar created an other test project for the GIT-master
Branch with some additional resources and an other wording for the
"slug-phrase". I'm very comfortable with the new naming and think
about renaming the resources for the other two branches : 2.2.x and
2.1.x

Could anybody have a look at the list
(https://www.transifex.com/projects/p/geoserver_test/resources/) of 26
resources (at the moment) and comment whats missing.

@Developers:
In addition, would it be possible to add a ".tx" folder of the
geoserver-root, that contains a config file for transifex client tool
for easy synchronization of the translated properties files? It would
look like this :
https://raw.github.com/fgdrf/gs-transifex-config/master/gs-2.2.x/config

@Astrid: Could you please review as well. What do you think about
technical terms and its translations. What do your customers think
about?

Cheers,
Frank

2013/1/1 Stefan Engelhardt (HBT) <Stefan.Engelhardt@anonymised.com>:

Hi list,
I am the "bad" user who pointed Andrea to the Transifex translations.

I hope that the way back from Transifex to GIT works fine in near future
because I now finished the missing part of the German translation.

Perhaps someone feels free to give me some comments about the
translation quality. I had some difficult decisions to do which
technical terms to translate or not.

Wish you all a happy new year!

Cheers
Stefan

-----Original Message-----
From: Oscar Fonts [mailto:oscar.fonts@anonymised.com]
Sent: Monday, December 31, 2012 7:07 PM
To: Andrea Aime
Cc: GeoServer Mailing List List
Subject: [bulk]: Re: [Geoserver-users] Translations on transifex

Hi,

I prepared a little script that automatically links transifex
resources with the corresponding properties files on git repo.
Once automatically linked, simply pulling from tx and pushing to git
would synchronize the contents.

This method is meant to be automatic and exhaustive mapping. It
locates 26 translation resources instead of 15, but their names are
different, because they are generated automatically from file paths.

The script: https://gist.github.com/3918745

And the transifex repo generated from git contents:
https://www.transifex.com/projects/p/geoserver_test/

So, if we adapted the actual transifex project to use the script, it
could be run periodically, for example as part of the release process.

I can put some time to test & document this better, coordinated with
actual mantainer. Frank? Chris?

Auguri,

Oscar.

2012/12/31 Andrea Aime <andrea.aime@anonymised.com>:
> Hi all,
> a user pointed me back to the Transifex translations for GeoServer:
> https://www.transifex.com/projects/p/geoserver_22x/
>
> Hum... I see there is a number of them growing. What happens when a
> translation
> hits 100%, how is it turned back to property files and merged into
the
> GeoServer sources?
>
> Cheers
> Andrea

-----------------------------------------------------------------------

-------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills

current

with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

------------------------------------------------------------------------------
Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
and more. Get SQL Server skills now (including 2012) with LearnDevNow -
200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
SALE $99.99 this month only - learn more at:
http://p.sf.net/sfu/learnmore_122512
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Hi,

to ISO-8859. Could anybody give me a hint to change the default
encoding from UTF-8 to ISO-8859 for such resources at build time. In
[...] I guess this would break the encoding for the German language
properties files...

You can keep the properties files in ISO-8859.

For the build to work, you have to make a little change in src/web/core/pom.xml:
https://github.com/oscarfonts/geoserver/commit/b172716e86536ddfad8485a55eb479be8d74e58e#L1L147

Chris and Oscar created an other test project for the GIT-master
Branch with some additional resources and an other wording for the
"slug-phrase". I'm very comfortable with the new naming and think
about renaming the resources for the other two branches : 2.2.x and
2.1.x

Applied a regex to search for all translation files:
(.*)/src/main/(resources|java)/GeoServerApplication.properties

And generated the tx project (.tx folder contents) from its matches.

Try the script, and if it works for you, I'd ask to include it in the
repo as well.

Cheers,

Oscar.