lilypond-devel
[Top][All Lists]
Advanced

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

Re: Broken Spanish documentation


From: John Mandereau
Subject: Re: Broken Spanish documentation
Date: Sat, 25 Aug 2007 22:55:25 +0200

Le mercredi 22 août 2007 à 00:03 +0200, Francisco Vila a écrit :
> El mar, 21-08-2007 a las 10:13 +0200, John Mandereau escribió:
> 
> > Maybe this is caused by your recent change to @documentencoding in
> > es/user/lilypond.tely (UTF-8 -> utf-8) -- why did you want to write the
> > encoding lower-case?
> 
> Mmm... let's have a closer look to the originals and their translations.
> 
>       Documentation/user$ grep -i documentencoding *
>       lilypond-program.tely:@documentencoding utf-8
>       lilypond.tely:@documentencoding utf-8
>       music-glossary.tely:@documentencoding UTF-8
> 
> This gives 2-1 for lowercase vs. uppercase.
> 
>       Documentation/es/user$ grep -i documentencoding *
>       lilypond.tely:@documentencoding utf-8
> 
> 1-0 for lowercase, but the other two files do not exist in the es/user
> directory.
> 
>       Documentation/es/user$ grep utf *
> 
> Here the results vary randomly between the two following versions:
> 
>       @c -*- coding: utf-8; mode: texinfo; documentlanguage: es -*-
>       @c -*- coding: utf-8; mode: texinfo; -*-
> 
> The GREP-ing in the originals gives only the second of these, of course.
> 
> And now
>       Documentation/user$ grep UTF *
> 
> The only meaningful result here is 
> 
>       music-glossary.tely:@documentencoding UTF-8
> 
> Is this all of any usefulness?

Not really; what matters is which case (upper- or lower-) works.  My
recent commit messages to Git tell you all the details -- pull then do
"git log", and if you want to see a particular diff, do "git show
<COMMITTISH>".

HTH,
John





reply via email to

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