[flup to list]
[EMAIL PROTECTED] writes:
> > > > > because the font-relative-size doesn't work.
> > > >
> > > > bugreport please?
>
> I've attached an tar.gz archive with 4 issues which appear
> (as far as I understand) to be bugs. details are in the 00_REPORT.txt
ok. thanks.
>1. font-relative-size seems to be ignored in \property ChordNames.ChordName
> see tester1.ly & tester1.ps
> Workaround: use font-magnification instead
I've added
@refbugs
Chord name printing implementation has been rewritten in 1.7. In 1.6,
ChordNames internally generate markup texts with font changes.
One of the results is that manually setting @code{font-relative-size}
will have no effect; use @code{font-magnification} in this case.
to the manual
>2. Chord names are typeset by default too close to composer name
I've set ChordNames.minimumVerticalExtent to (0 . 2.5) by default.
I'm not sure if this is the best solution, it might mean that chord
names take up too much space in other contexts.
>3. Under some conditions (in most cases for me but could not determine
> exactly) chord names are typeset too close to the volta lines
> (could be because of font-magnification)
Do I recall correctly that chords should be below the volta? That
seems like a better solution to me. I'll look into that.
>4. Spurious error messages are generated if the \paper section
> is missing before the \midi section; the ps & midi files seems to be OK
> see tester4.ly, tester4.ps & tester4.mid
> Workaround: ignore the message, the output files look OK
Works for me on lily 1.7
BTW, for bugreports, you can simply send the .ly and bug description
in a mail to the list. .ps is not necessary.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.cs.uu.nl/~hanwen
_______________________________________________
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
