bug-lilypond
[Top][All Lists]
Advanced

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

Re: lilypond-book via dvi and ps no longer seems to work


From: Ralph Palmer
Subject: Re: lilypond-book via dvi and ps no longer seems to work
Date: Fri, 10 Aug 2012 08:32:33 -0400

On Sat, Aug 4, 2012 at 11:17 AM, Laura Conrad <address@hidden> wrote:

>
> The manual
> <
> http://lilypond.org/doc/v2.15/Documentation/usage/invoking-lilypond_002dbook
> >
> says:
>
> To produce PDF output via LaTeX/dvips/ps2pdf, you should do
>
> lilypond-book yourfile.lytex
> latex yourfile.tex
> dvips -Ppdf yourfile.dvi
> ps2pdf yourfile.ps
>
> This no longer seems to work.  When I do this on the attached file (the
> same one I sent yesterday to complain about the line length in landscape
> mode), I get:
>
> ps2pdf test.ps test.pdf
> Error: /invalidfileaccess in --file--
> Operand stack:
>
>  
> (/home/newlily/lilypond/usr/share/lilypond/current/fonts/otf/CenturySchL-Ital.otf)
>   (r)
> Execution stack:
>    %interp_exit   .runexec2   --nostringval--   --nostringval--
> --nostringval--   2   %stopped_push   --nostringval--   --nostringval--
> --nostringval--   false   1   %stopped_push   1910   1   3   %oparray_pop
> 1909   1   3   %oparray_pop   1893   1   3   %oparray_pop   1787   1   3
> %oparray_pop   --nostringval--   %errorexec_pop   .runexec2
> --nostringval--   --nostringval--   --nostringval--   2   %stopped_push
> --nostringval--
> Dictionary stack:
>    --dict:1161/1684(ro)(G)--   --dict:0/20(G)--   --dict:79/200(L)--
> --dict:102/300(L)--   --dict:43/200(L)--
> Current allocation mode is local
> Last OS error: 2
> Current file position is 46293
> GPL Ghostscript 9.04: Unrecoverable error, exit code 1
>
> I don't think it matters that much whether it works or not, but if it
> isn't going to be fixed, it should be removed from the documentation.
>

Thanks for reporting this, Laura.

Developers - should this (and perhaps issue 2732) have been submitted as a
different Type? I confess that I don't know what constitutes a "Critical"
defect or a "defect in the core program".

This has been submitted as issue 2733 :
http://code.google.com/p/lilypond/issues/detail?id=2733

Ralph


reply via email to

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