Re: German translation of the manual

[John Mandereau]

Le jeudi 22 mars 2007 à 19:25 +0200, Till Rettig a écrit :
> Hi John,
> I think at the weekend I will deliver my first part of the translation. 
> Still there are some questions. Following the mailing lists I read that 
> you want to make a translation branch. Does this change my working? Will 
> I have to commit to master or to the other branch?

I suppose that by committing to master, you mean commmitting to your
local master branch, as you don't have push access to git.  You can go
on working on master (or mymaster, or whatever your branch is called)
locally, but from now you should pull from the branch named
lilypond/translation (instead of master) on git.sv.gnu.org.  If this is
not clear to you, tell me how are named the branches on your Git
repository, I'll tell you which exact command to use for pulling.


> Another question concerns the translation itself: You didn't mention 
> @cindex commands.

AFAICS it's mentioned in Documentation/TRANSLATION.


>  I saw that the french translation left them in 
> english, while the spanish translation team translated them also. What 
> should I do here?

You can safely translate them in the .itely source.  The French team
hasn't done it because when we started, we were not sure about how to
translate them, and I haven't explicitly told them to do so since then.

I upload every so often a build of lilypond/translation documentation to
http://john.mandereau.free.fr/lilypond-doc/Documentation ; you may check
how fresh it is at http://john.mandereau.free.fr/lilypond-doc/COMMITTISH

The Spanish index doesn't appear, and there are other buglets; I'll
hopefully fix all this before next release.


>  Wouldn't it be clever to also automate their 
> translation by a script, if I understand right, that they will form the 
> index?

makeinfo does it for free in all languages, so we don't need to write
another ugly script like the node name hacks.

Cheers
-- 
John Mandereau <address@hidden>