Re: FW: [frogs] Re: Patching the output file naming code (Was: thanks to whomever put this in the LSR...)
> > -- Forwarded Message > From: Ian Hulin > Reply-To: > Date: Sat, 20 Jun 2009 17:25:42 -0600 > To: Reinhold Kainhofer , > Conversation: [frogs] Re: Patching the output file naming code (Was: thanks > to whomever put this in the LSR...) > Subject: [frogs] Re: Patching the output file naming code (Was: thanks to > whomever put this in the LSR...) > > Hi Reinhold, > > I've now started doing some work on this, and the big disadvantage with the > current use of #(define output-suffix "whatever") et al. is that they > affect > all the files in all \score or \bookpart sections. What I would like to do > is pick up a value of the property from something like a \paper block > within > the current \score or \bookpart. Perhaps you're looking for ly:output-def-lookup ? paper and midi (and layout) blocks are all output-defs. Joe ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: RFC: new vertical layout engine
A quick update on the new vertical spacing: the version now in dev/jneeman has most of the features that I had planned (although there are still lots of loose ends to tie up). In particular, you can - space staves in groups using \override StaffGroup.StaffGrouper #'after-last-staff-spacing = #'((space . 50) (stretchability . 2)) - change the alignment of lyrics (for example) with \override Lyrics.VerticalAxisGroup #'staff-affinity = #DOWN - adjust the position of the top staff using first-system-spacing in the paper block I haven't yet done Andrew's request to stretch the last page with the same force as the previous page. Anything I've missed? Joe ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
new website: initial comments
Here's a very rough initial draft of our new website: http://percival-music.ca/blogfiles/out/lilypond-general_1.html Any comments or offers of help? At the moment, I'm looking for overall design issues, like "you should have a `blarg' section on the main menu" or "I can't find the current documentation on this new website". If you have any requests, go ahead and list them, although (as always) I will highly filter these requests with respect to our available resources. Requests which are accompanied by offers of help will almost certainly make it through the filter. :) Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
