Sven Axelsson <[email protected]> writes:
> On 24 February 2013 03:42, David Kastrup <[email protected]> wrote:
>
>> Now here is the rub: this is very clearly an encoding problem, and it
>> is a problem occuring only for particular characters for you. To
>> reproduce it accurately, it is very important that we have byte for
>> byte the same file to check that you have. So it is not sufficient
>> to include the file in your mail text, rather you have to send it as
>> an "attachment" to your mail. How to attach a file properly depends
>> on your mail client.
>>
>> Please check how you fare with the file I attached. Does it work or
>> not? If not, send us the output of your LilyPond run, attached as a
>> PDF.
>
> Running the file David attached fails with this message:
>
> GNU LilyPond 2.16.2
> Processing `xxx.ly'
> Parsing...
> xxx.ly:2:18: warning: non-UTF-8 input
> title = "Lettre
> ? ?lise"
> xxx.ly:2:20: warning: non-UTF-8 input
> title = "Lettre ?
> ?lise"
>
> This very clearly shows what the problem is. Re-saving the file with
> proper UTF-8 encoding works fine and produces a correct PDF.
So much for my theory that a mail attachment is a guarantee for a
byte-for-byte faithful copy. On my side, the file was definitely
UTF-8-encoded.
I have to agree that what appears on Gmane (where I read this list) was
Latin-1 encoded however. Let's see whether sending to the list server
fares better.
Attached again.
--
David Kastrup
\header{
title = "Lettre à Élise"
}
\markup { }
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
