Considering to translate multiroutemap on Translatewiki

I believe we have resolved all the issues raised by Siebrand now. Have you looked into supporting .rst-files? I'm going to present use of multiroutemap in Joensuu, Finland on Tuesday, and was hoping it would be working until then, so that I could show how easy it is to translate, and perhaps tempt some of our other project partners to use/contribute to it.

Oh cool I didn't know you are coming to Finland.

The problem with RST is that it's not a i18n file format, but document format like word or wikitext. It seems to be similar to wikitext, so one solution would be to add the text into wikipages and use the page translation feature of Translate to translate them. Though, the syntax is not familiar to our translators and they might make mistakes with that.

In any case we can start with the Gettext files, and start sorting out the details with commit access, creating project description page and things like that. If you can catch me on IRC or Skype we can do that more efficiently.

Ok, we can start with the Gettext files, but if it's not too much hassle, I'd just set up translating of the .rst files through wikipages. We can look through them before they go into production. As for the rest:

1. Commit access: I assume Sarah should give Siebrand push access?
2. Project description: I've made a draft here. Could you make a "logo" based on your top right icons (or something more "proper" if you like) Sarah? Should have a short description when the long one is done.
3. Sarah has changed the name from "multiroutemap" to "waymarked-trails-site" on Github. I think we should call it "Waymarked Trails" and "waymarked-trails" if lower case and sans space is needed.
4. New languages are added by adding them on new line around here.

I've chatted with Nike on IRC, and he wishes for himself and Amir (Amir will probably become the committer) to also get push access, to increase flexibility I presume.

Nike, Amir and Siebrand should have push access now.

I've finalized the draft project description including icons from the project as an illustration/logo.

Sarah says rst is not set in stone, Django can also do markdown and textile out of the box. Suggest you create an example what you can produce and then she can have a look on how to integrate it, but the help pages can be implemented afterwards.

I suppose the page translation feature is used on web interface? I think that could be useable for the help pages. We do not have to use RST, markdown is more similar to MediaWiki syntax and for example headings can be formatted exactly the same way. I suppose most effort would go in to importing the existing translations and setting up an export to translated files.

Page translation is not the best option here, I think. It does not have export capabilities and requires too much manual maintenance. You could use page translation if you were to install your own MediaWiki instance with Translate, but if you want the translations in your SCM solution, you need an FFS class (File Format Support).

Sarah has suggested to move the help pages to gettext files for translation here. However, presuming that we managed to get them into a separate template file, could we then also have them in a separate group the way it is done with OpenStreetMap and potlatch? That way UI and help page messages aren't mixed, and translators could easier prioritise the UI.

Yup they would be in separate groups, but under one top-level group.