Hi,<br>  just to clarify my position: I don&#39;t pretend to substitute the currently used gettext .po files that are used for the GUI, but only the Wiki pages (also, I agree with your comment about Launchpad, etc.). I strongly believe in &quot;using the right tool for the task&quot;. In the same way that I don&#39;t agree with the decision that was taken to convert the tutorials to .po files for translation, and then converting them back again to svg format, I would not find it &quot;logical&quot; to convert the wiki texts to .po and then back again. I think that that would be a waste of effort if there already is an easier way to automate the task.<br>

<br>  I don&#39;t have any experience using translatewiki (yet), so I don&#39;t know if it really would be an easier way to keep inkscape&#39;s wiki translations up to date. Could you shed some light here?<br><br>  Cheers,<br>

<br><div class="gmail_quote">2010/8/19 helix84 <span dir="ltr">&lt;<a href="mailto:helix84@...150...">helix84@...150...</a>&gt;</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">

Hello Lucas,<br>
<br>
I personally prefer .po files because I&#39;m most efficient with them as<br>
opposed to different web interfaces like Launchpad, Pootle,<br>
Translatewiki etc. But I understand other, especially novice<br>
translators might be more comfortable with those. I have no problem<br>
with adopting and supporting a website as an alternative translation<br>
platform but I expect the good old way to remain available.<br>
<br>
I&#39;ve been using Translatewiki to translate MediaWiki for a few years<br>
now and I&#39;ve seen its development. Are there any specific question you<br>
would like to ask?<br>
<br>
Regards,<br>
<font color="#888888">~~helix84<br>
</font></blockquote></div><br>