lilypond-user
[Top][All Lists]
Advanced

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

Re: (semi-OT) making tabloid-sized booklets


From: Christian Conkle
Subject: Re: (semi-OT) making tabloid-sized booklets
Date: Sun, 14 May 2006 22:12:27 -0500
User-agent: Mozilla Thunderbird 1.0.8 (X11/20060429)

By the way, I'm sorry for not having had time to finish productionizing
my PostScript patches. I expect I'll have time in late May.

It is possible (even likely!) that using my patch is causing a problem
for the psbook|psnup stage. Can you try without my patch to confirm?

Also, does the psnup output look correct in gv if you change the
viewing paper size?

--jhawk

Now that I've finished the project (recording session Weds!), I've got some time to devote to debugging. I'm thinking of writing a guide to preparing a full orchestral score, since it took me rather a while to figure everything out; it'd be nice to have all the relevant bits in one place.

I switched to 2.8.1; the problem for that version (with and without your patch--I'm making tabloid/letter booklets, not 9x12) is a bit different. The Postscript output of Lilypond, after being rearranged by psbook (and also after psnup), crashes Ghostscript with the following error:

ERROR: /rangecheck in --get--
Operand stack:
   names   --nostringval--   1   2579   --nostringval--   9
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- --nostringval--
Dictionary stack:
--dict:1119/1686(ro)(G)-- --dict:0/20(G)-- --dict:91/200(L)-- --dict:53/72(ro)(G)-- --dict:10/30(L)--


I simply set up my Makefile to build a PDF first, run it through pdftops, and make the booklet from that file. The result looks funny in gv: text is "washed-out" (white parts) and rendering is slow. However, Acrobat reads (and, more importantly, prints) just fine. (Once I figured out how to have it actually print onto 11x17 paper: on OSX it's in a dialog completely seperate from "Print"!)

-Christian






reply via email to

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