Re: Translation string problem

[Francisco Vila]

2008/12/10 Carl D. Sorensen <address@hidden>:
> On 12/9/08 6:12 PM, "Francisco Vila" <address@hidden> wrote:
>> Yes, because the problem is that explicitly created staves have to be
>> given English names 'up' and 'down' if they are to be used for the
>> autochange feature. This is illustrated with a single example in NR
>> 2.2.1 after the warning Trevor wrote yesterday.
>
> Seems to me that to avoid this problem we should never have LilyPond names
> that are standard English words.
>
> I think we should change the defined names "up" and "down" to "upperStaff"
> and "lowerStaff" or something like that.  Those names would be less
> confusing than "up" and "down", and wouldn't be subject to translation,
> because they're not English words.

Translation is not automatic, we translators do it. Any names you can
imagine would be subject to translation as long as they are variables,
comments, or context names and they go to the PO file.

I must add that the mechanism implemented by John to translate
everything inside the snippets works like a charm and gives to the
docs a true localized feeling.
-- 
Francisco Vila. Badajoz (Spain)
http://www.paconet.org