Hello, all!<br><br><div><span class="gmail_quote">2008/4/23, Ricky Zhou <<a href="mailto:ricky@fedoraproject.org">ricky@fedoraproject.org</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Another good example is OpenSUSE<br> (<a href="http://en.opensuse.org/Welcome_to_openSUSE.org">http://en.opensuse.org/Welcome_to_openSUSE.org</a>). I don't know how they<br> manage things, but seem to have extremely complete and well-updated<br>
translations of their wiki (not that I want us to have per-langauge<br> subdomains like they do).<br> <br></blockquote></div><br>At the first glance, that solution seems to be very interesting.<br>But see:<br><a href="http://en.opensuse.org/OpenSUSE_Translation_Guide">http://en.opensuse.org/OpenSUSE_Translation_Guide</a><br>
and/or<br><a href="http://pt.opensuse.org/OpenSUSE_Translation_Guide">http://pt.opensuse.org/OpenSUSE_Translation_Guide</a><br><br>AFAIK, how we can see at the links above, they use the same management than us. They just create a new page translated in their wiki and set up with a subdomain against us that we create a subdirectory (wiki/<LANG>/Page).<br>
<br>However, that continues to be a not easy way to make the source strings/messages available to the translators. <br>It's hard to manage the changes between the original page and a translated one, as we can see at the same links above, and as the currently pages of our wiki too.<br>
<br>Cheers<br clear="all"><br>-- <br>Diego Búrigo Zacarão<br>Linux User #402589<br>USE SOFTWARE LIVRE