yvand writes:
Hi lilypond developpers,
I wanted to type the well-known composition Für Elise in lilypond for a
friend.
Unfortunately, the PDF generated by lilypond was damaged (according to evince,
gimp, inkscape)! After some tests, I found what was the problem.
The title was Lettre à
Colin Hall colingh...@gmail.com writes:
Here is an update on your bug report, Yvand.
The bug you reported is due to a known problem in Ghostscript. The
Ghostscript team have fixed their software but we had not yet adopted
the fix in Lilypond. For more information, see:
Colin Hall colingh...@gmail.com writes:
David Kastrup writes:
Colin Hall colingh...@gmail.com writes:
Here is an update on your bug report, Yvand.
The bug you reported is due to a known problem in Ghostscript. The
Ghostscript team have fixed their software but we had not yet adopted
the
Le 27/02/2013 12:44, Colin Hall a écrit :
yvand writes:
Hi lilypond developpers,
I wanted to type the well-known composition Für Elise in lilypond for a
friend.
Unfortunately, the PDF generated by lilypond was damaged (according to evince,
gimp, inkscape)! After some tests, I found what was
YD writes:
Le 27/02/2013 12:44, Colin Hall a écrit :
yvand writes:
Hi lilypond developpers,
I wanted to type the well-known composition Für Elise in lilypond for a
friend.
Unfortunately, the PDF generated by lilypond was damaged (according to
evince,
gimp, inkscape)! After some
Le 25/02/2013 02:18, Thomas Morley a écrit :
2013/2/24 yvand yvand.sw...@gmail.com:
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
2013/2/25 yvand yvand.sw...@gmail.com:
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
The PDF is damaged. Evince 3.4.0 on debian wheezy
2) If you compile the lilypond file (with version 2.16.2), the PDF is
Francisco Vila paconet@gmail.com writes:
2013/2/25 yvand yvand.sw...@gmail.com:
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
The PDF is damaged. Evince 3.4.0 on debian wheezy
2) If you compile the
David Kastrup d...@gnu.org writes:
Jan Nieuwenhuizen jann...@gnu.org writes:
Frédéric Bron writes:
It is due to a bug in ghostscript. I submitted a bug report 29th of
Nov (2012) and it is now corrected. But it will take time until the
new version of ghostscript comes to everybody's
2013/2/25 David Kastrup d...@gnu.org:
I think this mainly depends on the version of Ghostscript that is being
used for converting PS to PDF (used internally by LilyPond when
generating PDF). The version of LilyPond, in contrast, is mostly
irrelevant with respect to the problem.
OK; so if
Francisco Vila paconet@gmail.com writes:
2013/2/25 David Kastrup d...@gnu.org:
I think this mainly depends on the version of Ghostscript that is being
used for converting PS to PDF (used internally by LilyPond when
generating PDF). The version of LilyPond, in contrast, is mostly
On Mon, 25 Feb 2013, David Kastrup wrote:
Francisco Vila paconet@gmail.com writes:
2013/2/25 David Kastrup d...@gnu.org:
I think this mainly depends on the version of Ghostscript that is being
used for converting PS to PDF (used internally by LilyPond when
generating PDF). The version
Martin Tarenskeen m.tarensk...@zonnet.nl writes:
On Mon, 25 Feb 2013, David Kastrup wrote:
Francisco Vila paconet@gmail.com writes:
2013/2/25 David Kastrup d...@gnu.org:
I think this mainly depends on the version of Ghostscript that is being
used for converting PS to PDF (used
It is due to a bug in ghostscript. I submitted a bug report 29th of
Nov (2012) and it is now corrected. But it will take time until the
new version of ghostscript comes to everybody's distribution.
Do you have a patch to go with this? We could put the patch into GUB
right away.
Do you mean
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,
Sven Axelsson sven.axels...@gmail.com writes:
On 24 February 2013 03:42, David Kastrup d...@gnu.org 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
David Kastrup d...@gnu.org writes:
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
2013/2/24 David Kastrup d...@gnu.org:
David Kastrup d...@gnu.org writes:
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)
Le 24/02/2013 02:19, Thomas Morley a écrit :
2013/2/24 yvand yvand.sw...@gmail.com:
Hi lilypond developpers,
I wanted to type the well-known composition Für Elise in lilypond for a
friend.
Unfortunately, the PDF generated by lilypond was damaged (according to evince,
gimp, inkscape)! After
On Feb 24, 2013, at 12:12 PM, yvand wrote:
Le 24/02/2013 02:19, Thomas Morley a écrit :
2013/2/24 yvand yvand.sw...@gmail.com:
Hi lilypond developpers,
I wanted to type the well-known composition Für Elise in lilypond for a
friend.
Unfortunately, the PDF generated by lilypond was
The archives at lists.gnu.org can be downloaded in mbox format.
Examining these, both attachments of your mails are encoded in
iso-8859-1. So it's either the mailing list or gnus.
Just as a test a hopefully utf8 encoded file is attached.
Felix
\header{
title = Lettre à Élise
}
\markup { }
yvand yvand.sw...@gmail.com writes:
I tested on my xubuntu 12.04.2 LTS with lilypond 2.14.2 and it works !
The problem occurs (as described in the original mail) on my archlinux
using lilypond 2.16.2 (package installed : community/lilypond
2.16.2-1) (changing \version in the .ly file makes
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
Il 24/02/2013 21:41, yvand ha scritto:
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
2013/2/24 yvand yvand.sw...@gmail.com:
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
I suspect URL:http://code.google.com/p/lilypond/issues/detail?id=2985,
and if that is the problem, it would likely go away if you used some
non-Latin-1 characters, like ἦ or so in the same string as well.
It is due to a bug in ghostscript. I submitted a bug report 29th of
Nov (2012) and it is
Frédéric Bron writes:
It is due to a bug in ghostscript. I submitted a bug report 29th of
Nov (2012) and it is now corrected. But it will take time until the
new version of ghostscript comes to everybody's distribution.
Do you have a patch to go with this? We could put the patch into GUB
Jan Nieuwenhuizen jann...@gnu.org writes:
Frédéric Bron writes:
It is due to a bug in ghostscript. I submitted a bug report 29th of
Nov (2012) and it is now corrected. But it will take time until the
new version of ghostscript comes to everybody's distribution.
Do you have a patch to go
Hi lilypond developpers,
I wanted to type the well-known composition Für Elise in lilypond for a
friend.
Unfortunately, the PDF generated by lilypond was damaged (according to evince,
gimp, inkscape)! After some tests, I found what was the problem.
The title was Lettre à Élise (translation in
2013/2/24 yvand yvand.sw...@gmail.com:
Hi lilypond developpers,
I wanted to type the well-known composition Für Elise in lilypond for a
friend.
Unfortunately, the PDF generated by lilypond was damaged (according to evince,
gimp, inkscape)! After some tests, I found what was the problem.
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 é, É, è, È, ç, Ç,
ù, Ù, À
(à
31 matches
Mail list logo
