Joe Neeman [Fri, 27 May 2011 15:57:16 +0000 (18:57 +0300)]
Emit not-quite-cross-staff beams in the right context.
This is related to 1043 and possibly other bugs. Previously,
if a staff change happened immediately after the termination of
an auto-engraved cross-staff beam, then the beam was parented
to the wrong staff. Now, every beam is parented to the context
in which it began.
When notes overlap on the same pitch on the same MIDI channel,
re-arrange the note-off events for MIDI players that cannot handle
overlap, but if midiMergeUnisons = #t, merge such notes.
Allow for spaces in ttf font glyph names. Fixes #1562.
Apparently, the Verdana.ttf font that comes with Windows 7 SP1
has glyphs 571 and 571 using names "glyph 571" and "glyph 572", i.e.,
their glyph names contain spaces. This breaks the PostScript output.
Thanks to Chris Lidell and James Lowe for their help to nail this
bug.
Keith OHara [Tue, 24 May 2011 01:49:23 +0000 (18:49 -0700)]
Loose lines honor padding between systems
When placing a loose line (e.g. Lyrics) at the top or bottom of a
system, include as a constraint the padding to the neighboring
system or markup. Fix 1654.
Keith OHara [Tue, 24 May 2011 01:49:23 +0000 (18:49 -0700)]
Loose lines honor padding between systems
When placing a loose line (e.g. Lyrics) at the top or bottom of a
system, include as a constraint the padding to the neighboring
system or markup. Fix 1654.
Trevor Daniels [Thu, 12 May 2011 08:39:31 +0000 (09:39 +0100)]
Fix calculation of vertical offset when 'staff-padding is set
- fix 877: Ottava clefs may not look good
- the previous code incorrectly calculated the offset from
the staff rather than the parent; this happened to coincide
with the correct value for most parents but gave an incorrect
offset for OctavateEight above the F-clef
Trevor Daniels [Thu, 12 May 2011 08:39:31 +0000 (09:39 +0100)]
Fix calculation of vertical offset when 'staff-padding is set
- fix 877: Ottava clefs may not look good
- the previous code incorrectly calculated the offset from
the staff rather than the parent; this happened to coincide
with the correct value for most parents but gave an incorrect
offset for OctavateEight above the F-clef
Mike Solomon [Thu, 12 May 2011 23:28:24 +0000 (19:28 -0400)]
Fixes the assert problem caused by ledger line spanners.
This fix makes it such that ledger lines are not printed when
there is a no-line staff symbol. This makes sense, as a note
cannot be above or below the staff if the staff does not exist,
which means that ledger lines should not be used.
Mike Solomon [Tue, 26 Apr 2011 11:09:21 +0000 (07:09 -0400)]
Fixes cross staff issue with beam collision avoidance.
Beam collision avoidance is now turned off for "fake" cross staff beams
(those that are registered as cross staff because of auto-beaming but
are in fact not). Additionally, beams no longer process other
cross-staff beams as covered grobs.
Mike Solomon [Fri, 22 Apr 2011 15:29:33 +0000 (11:29 -0400)]
Update beam collision in the documentation.
Notify users that beam collision avoidance does not occur for cross
staff beams and suggest that users use manual beams for beams that
end right before a staff change.
James Lowe [Tue, 26 Apr 2011 21:39:28 +0000 (22:39 +0100)]
Doc: Adjusted CG Policy on @lilypond[] variables
As a reuslt of work on NR 3.2 Titles and Headers, it was necessary to
define some more explicit requirements for using the variables in the
@lilypond[ ... ] construct. Ssuch as removing staffsize
and page sizes within the actual @lilypond example which only add more noise
to the examples.
Also when the need to show taglines and/or page breaks and footers is required then
\book is needed in the example and this will result in unnecessary white space between top and bottom
of the page. So showing page breaking features or numbering examples becomes
problematic within the documentation.
The new @lilypond[papersize=X] variable allows for explicit page sizing without
the need to include it in the example itself. Allowing for better clarity.
The papersize=X takes variables from the scm/paper.scm else 'a4' is presumed.
Moved existing material to the front of this section so that it makes more sense
and added the new requirements for the various preferred variables.