bug-lilypond
[Top][All Lists]
Advanced

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

Re: Ghostscript fails with special characters in filename


From: Dénes Harmath
Subject: Re: Ghostscript fails with special characters in filename
Date: Sun, 9 Aug 2009 17:20:53 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

> 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 -dDEVICEHEIGHTPOINTS=841.89 
-dCompatibilityLevel=1.4  -dNOPAUSE -dBATCH -r1200  -sDEVICE=pdfwrite
-sOutputFile="./?\x91.pdf" -c .setpdfwrite -f "?\x91.ps"'...GPL Ghostscript SVN
PRE-RELEASE 8.57 (2007-03-15)
Copyright (C) 2007 artofcode LLC, Benicia, CA.  All rights reserved.
This software comes with NO WARRANTY: see the file PUBLIC for details.
WARNING: /Unicode /Decoding resource is not accessible but it is useful for
generating ToUnicode CMap.
Error: /undefinedfilename in (\305\\x91.ps)
Operand stack:

Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--  
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--  
--nostringval--   false   1   %stopped_push
Dictionary stack:
   --dict:1087/1123(ro)(G)--   --dict:0/20(G)--   --dict:69/200(L)--
Current allocation mode is local
Last OS error: 2
GPL Ghostscript SVN PRE-RELEASE 8.57: Unrecoverable error, exit code 1

`gs   -dSAFER  -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 
-dCompatibilityLevel=1.4  -dNOPAUSE -dBATCH -r1200  -sDEVICE=pdfwrite
-sOutputFile="./?\x91.pdf" -c .setpdfwrite -f "?\x91.ps"' failed (256)
error: failed files: "?\x91.ly"


It seems the invocation is incorrect, since issuing the command

gs   -dSAFER  -dDEVICEWIDTHPOINTS=595.28 -dDEVICEHEIGHTPOINTS=841.89 
-dCompatibilityLevel=1.4  -dNOPAUSE -dBATCH -r1200  -sDEVICE=pdfwrite
-sOutputFile="./ő.pdf" -c .setpdfwrite -f "ő.ps"

succeeds...

> Maybe 8.70 final has fixed the problem, as I can't seem to reproduce this
problem here...

Unfortunately I couldn't build it on OS X, and MacPorts doesn't have the most
recent version. I'll try it on Linux soon.





reply via email to

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