[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Translation string problem

From: till Rettig
Subject: Re: Translation string problem
Date: Tue, 09 Dec 2008 13:40:40 +0100


thanks for report, I didn't check on it. What if we use for this particular 
case @c KEEP LY and put the
up and down there. So other instantiations with the same name get translated 
correctly, where it doesn*t harm.

-------- Original-Nachricht --------
Datum: Tue, 9 Dec 2008 11:08:05 +0100
Von: "Francisco Vila" <address@hidden>
An: "Jean-Charles Malahieude" <address@hidden>
CC: lilypond-devel <address@hidden>
Betreff: Re: Translation string problem

2008/12/8 Jean-Charles Malahieude <address@hidden>:
> I think a warning would be useful, even for the English users, mentioning
> that this use of the autochange command *needs* the staves to be called "up"
> and "down".

I agree.

> Therefore I also removed the relevant lines in the pot and po files (on my
> working copy of git) in order to have them untranslated.
> #. Documentation/user/keyboards.itely:264 (context id)
> #. Documentation/user/keyboards.itely:273 (context id)
> but with no success.

As pot and po files are auto-generated, you'll have to do this
continuously. The only way I see is to warn this in some place and try
to remember it. We could also get rid of the @lilypond block and live
with only an @example which is freely translated on the sources, but
we'll lose the graphical example.

Francisco Vila. Badajoz (Spain)

lilypond-devel mailing list

Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]