[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Translation string problem
From: |
Jean-Charles Malahieude |
Subject: |
Translation string problem |
Date: |
Mon, 08 Dec 2008 21:45:18 +0100 |
User-agent: |
Thunderbird 2.0.0.18 (X11/20081119) |
Hi John, Paco and Till,
There is one specific case where "up" and "down" happen to be sort of
"reserved words": using the \autochange command as explained in section
2.2.1 Common notation for keyboards (Notation Reference), it appears
that if the verbatim of the snippet gets translated, users might wish to
name the staves in their own language (arriba/abajo, oben/unten,
haut/bas), they will obtain 4 staves.
I know there is an exception to almost every rule, but...
\new PianoStaff <<
\new Staff = "tic" {
\new Voice = "voce" {
\key g \major
\autochange \relative c' {
g8 b a c b d c e
d8 r fis, g a2
}
}
}
\new Staff = "tac" {
\key g \major
\clef bass
}
>>
...produces the enclosed image.
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".
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.
Cheers,
Jean-Charles
- Translation string problem,
Jean-Charles Malahieude <=
- Re: Translation string problem, Francisco Vila, 2008/12/09
- Re: Translation string problem, Trevor Daniels, 2008/12/09
- Re: Translation string problem, till Rettig, 2008/12/09
- Re: Translation string problem, Francisco Vila, 2008/12/09
- Re: Translation string problem, Francisco Vila, 2008/12/09
- Re: Translation string problem, Francisco Vila, 2008/12/09
- Re: Translation string problem, Jean-Charles Malahieude, 2008/12/09
- Re: Translation string problem, Francisco Vila, 2008/12/09
- Re: Translation string problem, John Mandereau, 2008/12/09