Devon Schudy [Sun, 30 Mar 2014 05:15:57 +0000 (01:15 -0400)]
Tuplet brackets should reliably not follow kneed beams, regardless of whether Beam::is_knee has been called yet.
This affects input/regression/tuplet-number-kneed-beam-horizontal-fit,
and the following:
{
\override TupletBracket.bracket-visibility = ##t
\times 1/2 { c8 c''' c c''' }
}
Is it safe to call Beam::is_knee in Tuplet_bracket::calc_position_and_height?
David Kastrup [Sat, 5 Apr 2014 14:29:57 +0000 (16:29 +0200)]
Issue 3880: bad number formatting in svg path output
This uses ly:format with "~4f" format string rather than format with
"~S" for formatting point lists. Note that "~4f" has a different
meaning in ly:format as compared to plain format. This is consistent
with other number formatting. Also does this for output of color.
The previous output was problematic when the number was an exact
fraction.
David Kastrup [Sun, 6 Apr 2014 12:55:40 +0000 (14:55 +0200)]
Issue 3898: parser.yy: move figure_list to chord_body
Figures failed to get recognized as music function arguments and possibly
in some other contexts. Moving them together with chords in < > style
gets rid of that problem.
David Nalesnik [Sat, 29 Mar 2014 12:25:40 +0000 (07:25 -0500)]
Bad positioning of tuplet numbers on kneed beams with Beam.positions override.
Previously, when Beam.positions was overridden, tuplet numbers on kneed beams
would automatically be placed according to the bracket instead of against
the beam. This happened because the check for whether the beam was kneed
or not returned false in such cases. This patch replaces that check.
It also:
--adds a regtest demonstrating behavior with Beam.position overrides
--removes some redundant code
Devon Schudy [Wed, 26 Mar 2014 18:58:20 +0000 (14:58 -0400)]
Fix infinite loop in Completion_heads_engraver at invalid measure position (issue 3888).
* Completion_heads_engraver now gives a programming_error instead of trying to make negative-duration notes.
* intlog2 with a nonpositive argument now gives an error instead of an infinite loop.
Devon Schudy [Mon, 10 Mar 2014 16:20:37 +0000 (12:20 -0400)]
Count MIDI ticks from the beginning of the score, not each staff independently.
This keeps MIDI output aligned for:
* Lyrics (issue 3878)
* Staves without Dynamic_performer (issue 3871)
* Staves that start late
* Scores that start with grace notes (issue 1412).
This accidental style assigns accidentals to _all_ pitches
(just as dodecaphonic does) but remembers them throughout
a whole measure.
This style is useful for different styles of contemporary notation
that want to make use of the non-tonal dodecaphonic style but don't
want to print so many redundant accidentals.
James Lowe [Fri, 27 Dec 2013 23:50:57 +0000 (23:50 +0000)]
Doc: NR add \chord to examples in A2
Issue 3755
Added new column to show a working example (also useful for Blind composers)
Minor layout quibbles with @multitable means using the @* (forced break)
for TexInfo commands - not strictly LP doc policy - to enhance clarity
Reduced the line-width slightly of the @lilypond examples simply to
help accommodate the extra column
James Lowe [Sun, 29 Dec 2013 05:46:45 +0000 (05:46 +0000)]
Doc: NR Tidy up of A4 - fretboard diagrams
Removed bar numbers - inappropriate for this section
Added an @appendixsubsec for each of the three pre-defined
fretboard instruments (Guitar, Ukulele and Mandolin) so as
to make it easier to find in the index but also to break up
the apparent 'wall' of fretboard diagrams when viewing the
Appendix.
James Lowe [Tue, 24 Dec 2013 06:52:22 +0000 (06:52 +0000)]
Doc: NR Updated Delayed Turn Snippet
Issue 3369
Suggestion from Arno Waschk
Simplification of original snippet
Note: This snippet will only work since 2.17 versions (where the /single
command has been implemented) and does not work on the 'current' LSR
(which is still at 2.14 as of this patch).
James Lowe [Tue, 31 Dec 2013 07:06:11 +0000 (07:06 +0000)]
Doc: Tidy up of chord-names-jazz.ly
Added a new context definitigon to remove the Bar Number Engraver
as it was clashing with the instrument names and looked messy.
As it was not actually pertinent to the example I thought this the
simplest method
Also tidied up the spacing of the information as per standard doc
guidelines
Urs Liska [Thu, 12 Dec 2013 10:16:10 +0000 (11:16 +0100)]
Web: Reword contactUsAbout macro
Providing information on new reviews/productions etc.
should be possible by simply writing an email to bug-lilypond.
Redirecting to the Bug Report guide is off-putting.
Janek Warchoł [Sat, 7 Dec 2013 21:58:06 +0000 (22:58 +0100)]
CG: remove information about frogs and frog meister
frogs list is dead, and the frog meister was a good idea
but it gets out of touch from reality (since a few months
previous Frog Meister didn't actually participate in development).
Werner Lemberg [Thu, 6 Mar 2014 06:19:49 +0000 (07:19 +0100)]
Issue 3876: Fix shape of G clefs
This patch simplifies the code for the double G clefs; it also fixes the
incorrect test of the `double_shift' parameter that caused the non-double
G clefs being drawn twice.
Recent FontForge warnings like
Internal Error (overlap) in clefs.G: Intersection failed!
or the ugly shape with a straight line instead of a curve in the left part
of the G clef are now gone: Drawing the shape twice triggered a bunch of
FontForge bugs.
Keith OHara [Sat, 8 Mar 2014 14:45:20 +0000 (15:45 +0100)]
Fix issue 3868: line-breaking makes short lines
Two simple fixes:
1) Always have some stretchability between notes
2) If there _is_ a completely unstretchable line, shorter than the line-width,
score it as a bad fit, not as a perfect fit (report large forces for stiff lines).
Either one would fix the problem; both seem to be good to have in the code.
David Nalesnik [Fri, 21 Feb 2014 00:15:47 +0000 (18:15 -0600)]
Issue 3860: Add command \justify-line
The command \fill-line spaces words taking word length into account
such that the following distances are equal: outside edge of outside
markup to center of adjoining markup; center to center of
neighboring interior markups. As a consequence, the space between
words is unequal when the lengths of the markups vary and/or there
are more than three markups in the line.
The following patch creates the command \justify-line, which spaces
markups to fill a line such that the space in between each pair is
constant. Collisions are prevented by ensuring that this distance
does not fall below the current setting of word-space.
projects / lilypond.git / log