On 24 February 2013 03:42, David Kastrup <d...@gnu.org> wrote:
> yvand <yvand.sw...@gmail.com> writes:
>
>> and the character "à" in the title was the origin of the problem!
>> (same problem
>> in other header fields)
>> It seems so odd, amazing for me that only this "special" character was the
>> problem. Indeed, other "special" characters (such as é, É, è, È, ç, Ç,
>> ù, Ù, À
>> (à uppercase!) etc) works fine!
>
>> Below is an example of code that generates a damaged pdf :
>
> This is not quite a minimal example.  Better is something like the
> attached file.
>
>
>
> 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.

Always look at the text in the log whenever Lilypond fails. It is
usually helpful.

-- 
Sven Axelsson

_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Reply via email to