[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: automatic scaling to landscape paper size leads to collisions
From: |
Colin Hall |
Subject: |
Re: automatic scaling to landscape paper size leads to collisions |
Date: |
Fri, 14 Dec 2012 10:48:12 +0000 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Thu, Dec 13, 2012 at 07:02:07PM +0100, pls wrote:
> Hey all,
>
> I just discovered a command line option that is not mentioned in the docs:
> It's possible to append "landscape" to a paper size, e.g.
>
> $ lilypond -dpaper-size=\"a6landscape\" inputfile.ly
>
> There are a few error messages and lots of warnings but basically it seems to
> work.
>
> Parsing...
> programming error: Cannot find key `"a6landscape"' in alist, setting to `#f'.
> continuing, cross fingers
> programming error: cannot evaluate "#f" in module "#<module b61fc630>",
> setting to "(148.0 . 105.0)"
> continuing, cross fingers
> ?
> Drawing systems...
> warning: cannot fit music on page: overflow is 35.344199
> warning: compressing music to fit
> ?
>
> I tested the command with different large scores with many
> staves/instruments. With the landscape-option larger scores collide with the
> title and the copyright tag, staves collide and are compressed too much.
> Without the landscape-option the automatic scaling always seems to work. Same
> result when I include either
>
> #(set-default-paper-size "a6" 'landscape)
> or
>
> #(set-default-paper-size "a6landscape")
> in the .ly file. Automatic scaling does not seem to have an effect on the
> staff size?! Is this a "landscape-bug"?
>
> hth
> patrick
Thanks for the bug report, Patrick. Looks like that must have been
pretty painful.
I have created a tracker for the issue here:
http://code.google.com/p/lilypond/issues/detail?id=3023
Cheers,
Colin.
--
Colin Hall