Re: Ghostscript fails with special characters in filename

2009-09-29 Thread Harmath Dénes
The recently released 2.13.4 dev version handles all characters perfectly! Thank you! ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Ghostscript fails with special characters in filename

2009-08-23 Thread Ian Hulin
Hi Reinhold, I've tried your patch for ly:format and ~S here. Reinhold Kainhofer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Samstag, 22. August 2009 15:57:51 schrieb Ian Hulin: Hi Patrick, Reinhold, Patrick McCarty wrote: On 2009-08-21, Ian Hulin wrote: Patrick McCarty wrote:

Re: Ghostscript fails with special characters in filename

2009-08-23 Thread Ian Hulin
Hi Reinhold, Reinhold Kainhofer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Ian, On Sunday 23 August 2009 13:20:17 Ian Hulin wrote: Hi Reinhold, I've tried your patch for ly:format and ~S here. The latest one which also escapes ? Yes. It looks like a filename with quoted

Re: Ghostscript fails with special characters in filename

2009-08-23 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 23 August 2009 16:22:04 Ian Hulin wrote: Here is the tail of the output from the quoted version, there are loads more calls to ly_format and then it enters the routine and hangs. Ah, are you sure you applied the path to absolutely latest

Re: Ghostscript fails with special characters in filename

2009-08-23 Thread Ian Hulin
Reinhold Kainhofer wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 23 August 2009 16:22:04 Ian Hulin wrote: Here is the tail of the output from the quoted version, there are loads more calls to ly_format and then it enters the routine and hangs. Ah, are you sure you

Re: Ghostscript fails with special characters in filename

2009-08-21 Thread Ian Hulin
Patrick McCarty wrote: On 2009-08-20, Reinhold Kainhofer wrote: Am Donnerstag, 20. August 2009 11:47:52 schrieb Reinhold Kainhofer: Am Donnerstag, 20. August 2009 11:37:55 schrieb Patrick McCarty: On 2009-08-20, Reinhold Kainhofer wrote: To me this seems like guile is

Re: Ghostscript fails with special characters in filename

2009-08-21 Thread Patrick McCarty
On 2009-08-21, Ian Hulin wrote: Patrick McCarty wrote: Hmm... I just realized why the ~S was being used instead of ~a: the ~S allows double quotes in the filename, but ~a does not. So this would fail with your patch: $ lilypond \file\.ly Even though it is an unlikely filename,

Re: Ghostscript fails with special characters in filename

2009-08-21 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Freitag, 21. August 2009 23:20:12 schrieb Patrick McCarty: On 2009-08-21, Ian Hulin wrote: * You've identified a rare case which needs a fix to some pretty basic code. How do we know it's rare? I don't think it's worth breaking PDF

Re: Ghostscript fails with special characters in filename

2009-08-21 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Samstag, 22. August 2009 00:17:19 schrieb Reinhold Kainhofer: This works also with pathologic file names like: a b.ly b'c.ly cd.ly d'e.ly ef'.ly f\g.ly f\g.pdf g\'h.ly I just realized that we have no regression tests to check filename

Re: Ghostscript fails with special characters in filename

2009-08-20 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Donnerstag, 20. August 2009 03:41:57 schrieb ian_hulin: I've just been investigating this a bit more and have finally managed to install ghostscript 8.70 on my system. I have ghostscript 8.64 installed on my kubuntu system. If I compile a .ly

Re: Ghostscript fails with special characters in filename

2009-08-20 Thread Valentin Villenave
2009/8/20 Reinhold Kainhofer reinh...@kainhofer.com: So, basically, lilypond messes up the proper UTF-8 encoding of the external utility calls. OK, that is now in the tracker as http://code.google.com/p/lilypond/issues/detail?id=832 Regards, Valentin

Re: Ghostscript fails with special characters in filename

2009-08-20 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Donnerstag, 20. August 2009 10:48:09 schrieb Reinhold Kainhofer: Yes, I think that's the case here. It seems that gs is well able to handle 16- bit unicode characters, but it needs the correct file name. A little more playing around shows this:

Re: Ghostscript fails with special characters in filename

2009-08-20 Thread Patrick McCarty
On 2009-08-20, Reinhold Kainhofer wrote: Am Donnerstag, 20. August 2009 10:48:09 schrieb Reinhold Kainhofer: Yes, I think that's the case here. It seems that gs is well able to handle 16- bit unicode characters, but it needs the correct file name. A little more playing around shows

Re: Ghostscript fails with special characters in filename

2009-08-19 Thread ian_hulin
-with-special-characters-in-filename-tp24799271p25054809.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Ghostscript fails with special characters in filename

2009-08-09 Thread Dénes Harmath
Could you run lilypond --verbose on your file? That still looks a lot like #811; perhaps I'll Fwd it to the ghostscript team. The relevant section of the output of lilypond --verbose (2.12.2): Converting to `./ő.pdf'... Invoking `gs -dSAFER -dDEVICEWIDTHPOINTS=595.28

Re: Ghostscript fails with special characters in filename

2009-08-08 Thread Valentin Villenave
2009/8/4 Harmath Dénes harmathde...@gmail.com: No. It otherwise works perfectly on an Intel Mac. It only fails always with the mentioned characters. (Strangely, similar special characters, like ű or ê, work). Could you run lilypond --verbose on your file? That still looks a lot like #811;

Re: Ghostscript fails with special characters in filename

2009-08-08 Thread Patrick McCarty
On Sat, Aug 08, 2009 at 03:45:25PM +0200, Valentin Villenave wrote: 2009/8/4 Harmath Dénes harmathde...@gmail.com: No. It otherwise works perfectly on an Intel Mac. It only fails always with the mentioned characters. (Strangely, similar special characters, like ű or ê, work). Could you

Re: Ghostscript fails with special characters in filename

2009-08-06 Thread Dénes Harmath
On 2009.08.04., at 15:06, Valentin Villenave wrote: Er, I think it fails no matter the filename: http://code.google.com/p/lilypond/issues/detail?id=811 Regards, Valentin No, it otherwise works perfectly on an Intel Mac. It only fails always with the kind of mentioned characters. (Strangely,

Re: Ghostscript fails with special characters in filename

2009-08-04 Thread Valentin Villenave
2009/8/3 Dénes Harmath harmathde...@gmail.com: Some special characters (e.g. ő or đ) in the output filename cause gs to fail on OS X (10.5) and Linux (Kubuntu 8.10), under LilyPond 2.12.2 and 2.13.3 also. Er, I think it fails no matter the filename: