Considering to translate multiroutemap on Translatewiki

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.

Dittaeva (talk)22:01, 11 March 2012

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.

Guttorm Flatabø (talk)22:59, 5 May 2012

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).

Siebrand10:27, 6 May 2012

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.

Guttorm Flatabø (talk)12:52, 9 May 2012

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

Nike (talk)14:26, 9 May 2012