convert-ly rules for the vertical layout changes

View: New views
2 Messages — Rating Filter:   Alert me  

convert-ly rules for the vertical layout changes

by Bugzilla from reinhold@kainhofer.com :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Since the new vertical layout engine completely changes the way the layout
works, in particular, many paper variables no longer work and
VerticalAxisGroup #'minimum-Y-extent also no longer works, we really need
proper convert-ly rules to upgrade existing scores using the "old" vertical
layout settings to the new system.

Also, the default for non-stretching scores looks terrible, the staves are
always spaced only the absolute minimum allowed.
And with multiple scores in a larger file, the distance between one score, the
next piece title and the following score is way too small (the staves of the
two scores are spaced like they belonged to the same score, and the title is
squeezed in between that small space!).

Unfortunately, I don't have the time now to investigate better defaults
myself, but with these defaults, the scores simply look terrible.


Cheers,
Reinhold
- --
- ------------------------------------------------------------------
Reinhold Kainhofer, reinhold@..., http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFK6ZOVTqjEwhXvPN0RAiZlAKDERNFA1YDEWUDX1Jb84OHTpSpOawCeK7tS
UgGErbb0X8s4dSeE0DhFHtU=
=qaQm
-----END PGP SIGNATURE-----


_______________________________________________
lilypond-devel mailing list
lilypond-devel@...
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: convert-ly rules for the vertical layout changes

by Kieren MacMillan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Reinhold (et al),

> Unfortunately, I don't have the time now to investigate better  
> defaults
> myself, but with these defaults, the scores simply look terrible.

+1

Another problem I've found (but have yet to minimally-exemplify) is  
that a manual \pageBreak will often [always?] lead to a page with a  
single system and then an automatic page break, so (e.g.) what should  
fit on two pages, with the break manually forced, ends up on three  
pages instead.  =(

I'm right in the middle of reengraving [for the new spacing engine in  
2.13.6+] this summer's quartet score — hopefully I'll have good  
defaults to report soon.

Cheers,
Kieren.

_______________________________________________
lilypond-devel mailing list
lilypond-devel@...
http://lists.gnu.org/mailman/listinfo/lilypond-devel