bug-lilypond
[Top][All Lists]
Advanced

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

Re: "à" in title makes damaged pd f


From: yvand
Subject: Re: "à" in title makes damaged pd f
Date: Mon, 25 Feb 2013 10:40:13 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130221 Thunderbird/17.0.3

Le 25/02/2013 02:18, Thomas Morley a écrit :
2013/2/24 yvand <address@hidden>:
Le 24/02/2013 19:03, james a écrit :

the problem here is not in lilypond, nor in the file, exactly. The problem
is the character encoding. (You can look up character encoding on wikipedia
if you really want to know more about it.) More to the point: the best way
to help solve your problem would be to know which program you use to create
the lilypond file and then find out how to enable utf-8 by default in the
program.

I don't understand,
Well, we're discussing two problems

a) We can't trust in our encoding while communicating via mail or
looking up the the archives.
     That's horrible.
b) The problem you reported. James gave you some good advice.


the problem only occurs with this character and with
this version of lilypond ! (using the title "Lettre à Élise")
I use gedit to write lilypond files, the files are encoded in utf8.
I doubt.

To test under nearly the same conditions I installed 2.16.2, wrote
(not copied) the example and compiled it.
No problem.

Are you _really_ sure about your utf8 encoding?
How do you test it?

-Harm

Hi,

Thank you for helping me.
I tried to write the minimal code from scratch in nano, gedit, geany but the problem is still there! I downgraded lilypond package to 2.12.3 version and it works with the *exactly* the same file! I don't think this is an encoding problem!

To avoid encoding problem with mails, I hosted the file here : http://lucd.legtux.org/test.zip
Can you test :
1) The PDF is damaged
2) If you "compile" the lilypond file (with version 2.16.2), the PDF is still damaged

gedit and `file --mime-encoding test.ly` say that the file is well encoded en utf8.

A friend of me can reproduce the problem, under archlinux.

-yvand



reply via email to

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