John Hawkinson wrote:
Err, I'm not sure I follow.
If LilyPond is generating PostScript output, it needs to specify the
size of the rendered page in the PostScript. Otherwise the PostScript
is incomplete and cannot be properly processed by printers and by the
PDF generator both (this is why the LilyPond-produced PDF of a 9x12
page runs off the edge when viewed in Acrobat Reader). They can only
guess a paper size, either by their own default, or based on the
%%DocumentPaperSizes: DSC comment, which is just an advisory comment
(and, actually, DocumentPaperSizes is deprecated; instead LilyPond
should be generating a %%DocumentMedia comment, which can include
it does, at least 2.8 does.
actual page dimensions) and won't actually help with a printer (though
it might help with Acrobat Distiller or Ghostscript).
I don't think there were any printer-specifics in the code in my
email. It should work for any compliant Level 2 or Level 3 Postscript
I thought I saw ManualFeed in there? Doesn't that make sense only for
certain printers
Is there a reason you don't want to output the /PageSize info?
No, there's not. I'll gladly consider well written patches to deal with
arbitrary paper sizes. The relevant code is in paper.scm ; there needs
to be variant of
set-paper-size
which can deal with dimensions, eg. of the form (set-paper-size '((9 .
in) (12 . in)) 'landscape)
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user