lilypond-devel
[Top][All Lists]
Advanced

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

Re: white-dot / white-text


From: Carl Sorensen
Subject: Re: white-dot / white-text
Date: Sat, 04 Jun 2005 08:32:51 -0600

On Sat, 2005-06-04 at 12:59 +0200, Han-Wen Nienhuys wrote:

> I'm still confused: are the PDF files created by your own installed 
> Ghostscript, or with the GS bundled with LilyPond?

I assume they're created with the GS bundled with LilyPond.  When I open
up a command prompt window, there is no gs available.

When the pdf file is created, there is an error log created as well.
The error log is as follows:

# -*-compilation-*-
Processing `C:/Documents and Settings/Compaq_Owner/Desktop/fret-
diagram.ly'
Parsing...
Interpreting music... [8][11]
Preprocessing graphical objects... 
Calculating line breaks... [3][6][9]
Calculating page breaks...
Layout output to `fret-diagram.ps'...
Converting to `fret-diagram.pdf'...
`gs -dCompatibilityLevel#1.4  -sPAPERSIZE#"a4" -q -dNOPAUSE -dBATCH -
sDEVICE#pdfwrite -sOutputFile#"fret-diagram.pdf" -c .setpdfwrite -f
"fret-diagram.ps"' failed (1)
However, a pdf file was created, which was not correctly rendered.

I then opened up a graphical GS window (from my Windows installation)
and got the error information I was reporting earlier.

BTW, I'm now running again on Fedora Core 3.  I get a very similar error
when I run lilypond on this system with input/test/fret-diagram.ly.

address@hidden lilypond]$ lilypond input/test/fret-diagram.ly
GNU LilyPond 2.5.27
Processing `input/test/fret-diagram.ly'
Parsing...
Interpreting music... [8][11]
Preprocessing graphical objects...
Calculating line breaks... [3][6][9]
Calculating page breaks...
Layout output to `fret-diagram.ps'...
Converting to `fret-diagram.pdf'...
`gs -dSAFER -dCompatibilityLevel=1.4  -sPAPERSIZE="a4" -q -dNOPAUSE -
dBATCH -sDEVICE=pdfwrite -sOutputFile="fret-diagram.pdf" -c .setpdfwrite
-f "fret-diagram.ps"' failed (256)
error: failed files: "input/test/fret-diagram.ly"


I'm now going to try to identify which features of fret-diagram.ly are
causing trouble.

-- 
Carl Sorensen <address@hidden>





reply via email to

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