Re: Translation string problem

[Carl D. Sorensen]

On 12/10/08 1:37 AM, "Francisco Vila" <address@hidden> wrote:

> 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.

Then I imagine the problem must be that sometimes you want "up" and "down"
to be translated, but not in the autochange snippet.  So perhaps my
suggestion should just be to change the defined names for autochange staves
to "upperStaff" and "lowerStaff" so those words could be left out of the PO
file.

Or, we could just get the @KEEP LY working properly, which John has promised
to do.  So maybe my suggestion is not the right one.  At any rate, I think
we should have some system which does not require *any* exceptions to the
documentation standards -- not even one, localized, commented one.

Thanks,

Carl