Re: Documentation translation

[John Mandereau]

Le samedi 03 mars 2007 à 17:19 +0200, Till Rettig a écrit :
> Hi John,
> 
> I will now slowly start the translation of the documentation. I got 
> quite most things clear from your TRANSLATION file, many thanks to you 
> for that!

Well, I feel I only deserve half acknoweledgements, as this file is only
half done.


>  One thing is with the first file I started with: 
> lilypond.tely. Here is a lot of nodes that are not mentioned in the 
> nodenames hat should not be translated (with node I refer to the 
> expression between the @ sign and some word after. Is this better to be 
> called a field or command? Well, anyways, something like @title and so 
> on should probably be translated directly since it appears only one time 
> in the whole document.

@ is a prefix for all Texinfo commands, not only for node names.  You
may want to read Texinfo documentation to become more familiar with it;
a convenient way is to run Emacs and do C-h i


> Another question: Will there be a de.po file automatically generated, or 
> should I take the lilypond-doc.pot file and rename and translate it? I 
> guess the letter is right after checking its contents.

No, IIRC de.po is created automatically if you follow the instructions
in TRANSLATION.


> The language.po file should maybe still be added to the TRANSLATION 
> cathegoy 1 files (or at least partly)?

Maybe; the most important is that every node name/section title that
appears in existing translated docs are translated in the .po.


>  How does it influence the docs if 
> the po file is already completely translated but the documents it refers 
> to are not? Will the headers appear in the other language then?

It works on a per-page basis.  A single HTML page is generated for every
Texinfo node; node and section names (not only in the titles but also in
cross-references) are translated in the translated HTML pages.  See the
French docs to get some clues (preferably in the docs tarball so you
aren't annoyed by automatic language selection), it'll certainly be
clearer than any long explanation blurb.


Cheers
-- 
John Mandereau <address@hidden>