Use Translatewiki or Transifex for translation

[GoogleCodeExporter]

While it is fairly easy to translate OSMTracker directly for those of us 
technically inclined, it does not make for smooth updating or collaboration on 
translations.

I recently initiated translation of Waymarked Trails (http://hiking.lonvia.de) 
on translatewiki.net and we've had a tremendous response from the community 
there with around 30 complete translations in a few months.

While Translatewiki is cumbersome to get into, and might not like the XML-files 
Transifex is easy to set up and use, and is probably the best alternative for 
this project.

I've set up a couple of test projects there and could set up OSMTRacker too if 
this sounds interesting.

Original issue reported on code.google.com by dittaeva on 2 Aug 2012 at 2:43

[GoogleCodeExporter]

Oh, and both platforms are open source / free software.

Original comment by dittaeva on 2 Aug 2012 at 2:43

[GoogleCodeExporter]

Transifex looks interesting indeed, one drawback is that people will have to 
create an account, but I guess they already have to do so for Google Code or 
GitHub currently.

Could you setup the project and add me as a collaborator or something, so that 
I can have a look around ? My account is 'nguillaumin'. Cheers !

Original comment by nicolas@guillaumin.me on 5 Aug 2012 at 12:16

[GoogleCodeExporter]

Issue 192 has been merged into this issue.

Original comment by nicolas@guillaumin.me on 15 Aug 2012 at 12:07

[GoogleCodeExporter]

I started to play with Transifex but I got stuck with an issue about how 
Android suffixes resources with version numbers as well as language codes 
(values-fr/ and values-v11).

https://www.transifex.com/projects/p/osmtracker-android/

I'll come back to it soon and try to properly upload the translation files.

Original comment by nicolas@guillaumin.me on 15 Aug 2012 at 10:19

[GoogleCodeExporter]

I managed to upload all the files. The remaining issue now is that the buttons 
layout XML file is not in a format supported by Transifex, not sure how to deal 
with that...

Original comment by nicolas@guillaumin.me on 16 Aug 2012 at 12:05

[GoogleCodeExporter]

Sorry, first I didn't notice your reply and then I didn't have time, but it 
seems you have things under control anyway.

Original comment by dittaeva on 16 Aug 2012 at 5:25

[GoogleCodeExporter]

No worries, happy to make you "team leader" or whatever @ Transifex if you want 
to.

Do you have any idea about translating non Android XML files like the button 
layout one ?

Original comment by nicolas@guillaumin.me on 16 Aug 2012 at 5:37

[GoogleCodeExporter]

No, I don't have any idea about non Android XML (nor have I investigated). I 
have asked on Translatewiki if they will take us in though, they are in many 
ways functionally better and I think we'll get more translations from them and 
can share Translation memory and translators with the other OSM projects.

http://translatewiki.net/wiki/Thread:Support/Request_for_comment_on_feasability_
of_translating_OSMTracker_for_Android

Original comment by dittaeva on 16 Aug 2012 at 7:40

[GoogleCodeExporter]

Founder Nike writes: "We do not have support that file format at the moment, 
but looking at the files it looks like a hour or few hour job depending on who 
wants to implement support."

Original comment by dittaeva on 16 Aug 2012 at 8:08

[GoogleCodeExporter]

Transifex can be extended for new format: 
http://help.transifex.com/server/contributing.html#add-new-handler however I 
don't think they'd be interested for the specific XML format of our file. They 
would probably prefer a "generic" XML translator. Too bad it's in Python, I 
would have given it a shot.

I don't know about Translate Wiki, the process seems far less automated and as 
far as I understand translations are committed by an TranslateWiki team member, 
which makes it difficult to synchronise with Market releases.

Maybe I can put the labels from the XML file in a supported format, then have a 
script at build time that translate it back into the XML... I need to think 
about it.

Original comment by nicolas@guillaumin.me on 16 Aug 2012 at 8:20

[GoogleCodeExporter]

The fix was in issue #52: The layouts will now reference strings in a separate 
Android resource file, which can then be translated as the other ones.

Original comment by nicolas@guillaumin.me on 16 Aug 2012 at 12:19

[GoogleCodeExporter]

Well I guess that's it, I've uploaded all the translations to Transifex and 
updated the "Translating" wiki page, we'll see how that goes !

Thanks for the idea !

Original comment by nicolas@guillaumin.me on 16 Aug 2012 at 12:44

• Changed state: Fixed
• Added labels: v0.6.1