RE: [TSVN] doc translations

Hi Jean-Marc

> I understand that; what I don't understand is what *I* have to do with
> xml2po, libxml2 and python. Or was that info intended for Lübbe only?

I think, this mostly applies to me :-). I will test the toolchain and report
back as soon as possible. I see the following steps in the doc translation
process:

1) Docs are changed in the english version
2) A doc.pot file is updated from the new docs and checked into say
doc/Languages
3) Doc translators update their doc/Languages directory
4) Using poEdit, doc translators update their .po file from the current pot,
translate and check in (or send to the patches list)

Doc Translators will need the xml2something stuff only if they want to build
their language helpfiles themselves (for testing purposes)

> How do you want us to fill the .po file: leave not yet
> translated strings
> empty of fill them with english?

Leave them emptly, because...

> Will the doc generation stuff
> default to english for any missing .po entry?

... It'll default to english.

 
> And it will make it easier to reorganise the docs, as there is only a
> single set of XML master files; all translations being generated from
> that set, right?

Yes, that's the idea. Structural changes immediately go into each language,
there's no need for the translators to work on that. The only drawback is
that translators work out of context in poEdit, so you should have a current
version of the english docs at your side while translating.

Cheers
- Lübbe

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org