<div class="gmail_quote">2010/11/12 Paolo Cavallini <span dir="ltr"><<a href="mailto:cavallini@faunalia.it">cavallini@faunalia.it</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Il 12/11/2010 14:07, Alexander Bruy ha scritto:<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sphinx has a more simple syntax than Latex, but there are same problems<br>
with translation such as finding new strings to be translated<br>
</blockquote>
<br></div>
I think this is the main problem: currently we spend more time searching for what to translate than actually translating.<div class="im"><br></div></blockquote><div><br></div><div><br></div><div>Hi,</div><div><br></div><div>
just an idea: </div><div><br></div><div>For years, KDE has successfully used docbook XML for documentation and a couple of scripts to extract untranslated strings into a gettext PO catalog and to import them back into docbook. </div>
<div><br></div><div>The source was splitted to have each individual semantic unit in a single PO "msgid", this way a small change or fix in the source does not invalidate all the translation.</div><div><br></div>
<div>When I was in the translation team (I left a few years ago) the process was completely automatic, with cron jobs to keep everything in sync.</div></div><div><br></div><div>See:</div><div><a href="http://l10n.kde.org/docs/translation-howto/doc-translation.html">http://l10n.kde.org/docs/translation-howto/doc-translation.html</a></div>
<div><br></div>This method had the primary advantage to manage both GUI and doc translations with the same gettext toolchain, this way It was easier to keep translations coherent (think about fuzzy translations of the GUI menu strings).<div>
<br></div><div>docbook can be easily transformed into HTML (single and multi-page) , ODT, PDF etc.</div><div><br></div><div><br>-- <br>Alessandro Pasotti<br>w3: <a href="http://www.itopen.it">www.itopen.it</a><br>
</div>