On 4/9/06, Erlend Aasland <[EMAIL PROTECTED]> wrote:
> On 4/9/06, Erlend Aasland <[EMAIL PROTECTED]> wrote:
>
> >
> > On 4/9/06, Erlend Aasland < [EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > >
> > >
> > >
> > > These are 55% and 57.5% the size of one staff space (that would be about
> 12% and 15%
On 9-Apr-06, at 11:04 AM, Geoff Horton wrote:
I think the following messages to lilypond-users (as well as my own
complete inability to understand music functions) suggest that the
manual could use some work in this area.
A problem endemic to manuals, and one that I have no idea how to fix,
i
On 4/9/06, Erlend Aasland <[EMAIL PROTECTED]> wrote:
On 4/9/06, Erlend Aasland <
[EMAIL PROTECTED]> wrote:
These are 55% and 57.5% the size of one staff space (that would be about 12% and 15% of the original size). Smaller? I'll send examples that are 52.5% and 50% of one staff space in another ma
On 4/9/06, Erlend Aasland <[EMAIL PROTECTED]> wrote:
These are 55% and 57.5% the size of one staff space (that would be about 12% and 15% of the original size). Smaller? I'll send examples that are 52.5% and 50% of one staff space in another mail (so it won't bounce on the mailing list).
...here is
Greetings;
I've been working on a largish collection of hymns for the last several
years. The collection includes lead sheets, piano scoring, and
orchestral arrangements, and a hymnal. There are now several thousand
files in the source base. As you might imagine, automation is really
impor
On 9-Apr-06, at 3:13 AM, Mats Bengtsson wrote:
Index: lilypond/scm/define-grob-properties.scm
diff -u lilypond/scm/define-grob-properties.scm:1.157
lilypond/scm/define-grob-properties.scm:1.158
How about saying something like:
direction ,ly:dir? "#UP or #DOWN, #LEFT or #RIGHT? (or a numeri
The attached small patch has the effect of causing 'lilypond -H all' to
write out every field that appears in the header block of the score
being processed. This is useful for constructing various types of
indexes, such as the metrical index, composer index, and tune index
common in hymnals.
On 4/4/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> David Feuer wrote:
> > Why are properties set by default in the bottom context? I think it
> > would make more sense to do what Postscript does with dictionaries and
> > set them by default in the lowest context that has those properties
>
Joe Neeman wrote:
Hmm, doesn't that introduce scaling/dimension problems?
In what sense? Not within the constrained-breaker -- the demerits calculation
is purely internal so the only possibility of a scaling problem is with
externally introduced penalties.
No, but all components of the penalt
try
-b scm
David Feuer wrote:
Is there an option I can pass to LilyPond to get it to print out
representations of its stencils? I see code for something like that,
but I don't see how to activate it.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Soft
Index: lilypond/scm/define-grob-properties.scm
diff -u lilypond/scm/define-grob-properties.scm:1.157
lilypond/scm/define-grob-properties.scm:1.158
--- lilypond/scm/define-grob-properties.scm:1.157 Mon Apr 3 17:08:35 2006
+++ lilypond/scm/define-grob-properties.scm Sat Apr 8 22:42:45
11 matches
Mail list logo
