Ok, Frank's given me permissions and am playing around with this. Am
quickly hitting the limits of my translation / localization knowledge. I
have a question, which may in fact be what Frank was originally getting at
in this thread.
I am using transifex and getting the files from there, and when I do a diff
on what it produces I get a lot of changes, most of them more or less like:
-AbstractCoverageStorePage.description = Descripci\u00F3n
+AbstractCoverageStorePage.description = Descripci<F3>n
I _think_ this is because it is ISO-8859 instead of ASCII English.
So my questions
* Will this style work in GeoServer admin?
If yes,
* How would we feel about switching over to this style?
If no,
* Frank, did you figure out a way for transifex to get it in to GeoServer's
style?
On switching over, the argument in this favor is that doing so will make it
so even users could contribute to GeoServer translations, with no knowledge
of code. And then it'd just take a few minutes from a developer to create a
git pull request, and then even less time for a committer to review and
pull it in.
On Wed, Oct 17, 2012 at 1:20 PM, Chris Holmes <chol...@opengeo.org> wrote:
> Hey, so at OpenGeo we've been having some good experiences with Transifex,
> using it for our GeoNode project.
>
> We're still in a pretty sad state of translations relative to 1.x (I think
> we had 7 or 8 by the time we closed out 1.7.x, and we're at 4 right now in
> 2.x), and I think the type of tooling offered by Transifex could greatly
> improve our coverage.
>
> I was about to dig in to setting it up, when I noticed this thread, that
> it looks like Frank already has done so. See
> https://www.transifex.com/projects/p/geoserver_22x/
>
> Frank, could you add me as an admin for the geoserver project? I'm
> https://www.transifex.com/accounts/profile/cholmes/
>
> I think the most important step is to update the documentation -
> http://docs.geoserver.org/stable/en/developer/translation.html - with
> telling users to just use transifex. And then we need to explain how to go
> from transifex resources to pull requests (Jeff says the transifex
> commandline tools can help with this a lot, making git pull requests for
> you).
>
> Then a nice blog post calling for translators. I think with that we could
> get a lot of people translating if we set this up right.
>
> On Sun, Jan 22, 2012 at 1:57 PM, Andrea Aime <andrea.a...@geo-solutions.it
> > wrote:
>
>>
>>
>> On Sun, Jan 22, 2012 at 8:32 PM, Frank Gasdorf <
>> fg...@users.sourceforge.net> wrote:
>>
>>> Hello List,
>>>
>>> I'd like to discuss, how to handle properties files for geoserver.
>>>
>>> In the past, Christian
>>> (
>>> http://www.mail-archive.com/geoserver-devel@lists.sourceforge.net/msg12071.html
>>> )
>>> already started the discussion about UTF8 vs. some other encodings a
>>> while ago. While I has been working on German translations in the last
>>> weeks and month I was in close dialogue with translation specialists
>>> from transifex.net.
>>>
>>> Summarizing this communication:
>>> - standard expected encoding for java properties files readers and
>>> writers is ISO 8859-1 (http://en.wikipedia.org/wiki/ISO/IEC_8859-1),
>>> see see javadoc 1.4
>>> (http://docs.oracle.com/javase/1.4.2/docs/api/java/util/Properties.html)
>>> and 6 (
>>> http://docs.oracle.com/javase/6/docs/api/java/util/Properties.html)
>>> - "Characters that cannot be directly represented in this encoding can
>>> be written using Unicode escapes" (\uXXXX)
>>>
>>> I suggest to switch over to the ISO Standard encoding for properties
>>> files. I guess eclipse also uses per default ISO 8559-1, if the
>>> developer uses the Action "externalize Strings". IMHU it would be
>>> easier to work with third-party tools like transifex, that explicit
>>> working on the Java standards.
>>>
>>> BTW, if all characters are encoded by \uXXXX sequences, everything
>>> would be fine in the future.
>>>
>>
>> As far as I know writing the property files in some languages (japanese,
>> chinese) in ISO 8859-1 with escape codes can be really hard,
>> but afaik in those case the xml format for property files is the
>> preferred one.
>>
>> I'm not up to speed with what is going on with translations, is
>> everyone doing translations using this transifex.net site?
>>
>> As for coding, the coders only add strings to the main (english)
>> property file afaik (well, maybe Christian adds to the German one
>> as well, not sure), and we do so manually, the Eclipse code to externalize
>> the strings is of little help, does not work with our customized Wicket
>> i18n subclasses (nor it would work with the standard ones afaik).
>>
>> Anyways, I don't mind about the encoding, both work for me, provided
>> that we reach to an agreement that works for all translators.
>>
>> Speaking of which... who's doing translations and how?
>> As far as I can see the devs are doing the initial work in English,
>> then there is you and Ives that cover German and French respectively?
>> Anyone else?
>>
>> Cheers
>> Andrea
>>
>> --
>> -------------------------------------------------------
>> Ing. Andrea Aime
>> GeoSolutions S.A.S.
>> Tech lead
>>
>> Via Poggio alle Viti 1187
>> 55054 Massarosa (LU)
>> Italy
>>
>> phone: +39 0584 962313
>> fax: +39 0584 962313
>> mob: +39 339 8844549
>>
>> http://www.geo-solutions.it
>> http://geo-solutions.blogspot.com/
>> http://www.youtube.com/user/GeoSolutionsIT
>> http://www.linkedin.com/in/andreaaime
>> http://twitter.com/geowolf
>>
>> -------------------------------------------------------
>>
>>
>> ------------------------------------------------------------------------------
>> Try before you buy = See our experts in action!
>> The most comprehensive online learning library for Microsoft developers
>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
>> Metro Style Apps, more. Free future releases when you subscribe now!
>> http://p.sf.net/sfu/learndevnow-dev2
>> _______________________________________________
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>>
>
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
