David Kastrup [Fri, 1 Jun 2012 13:07:36 +0000 (15:07 +0200)]
Document <> and improve other simultanous music documentation.
This is a side issue of 2522: it improves the documentation dealing
with various ways of entering parallel music and gives the necessary
information to understand <> as a special case of chords.
Mike Solomon [Wed, 6 Jun 2012 03:32:06 +0000 (05:32 +0200)]
Simultaneous Scripts, Slurs, and TupletBrackets turn off collision resolution
When these three grobs occur at the same time, cyclic dependency problems
arise which sometimes cause layout irregularities. This patch turns off
collision resolution in tuplet-bracket.cc for this case, which solves the
layout problem. The cyclic dependency warnings persist, however, for
certain cases.
Benkő Pál [Sun, 13 May 2012 16:07:40 +0000 (18:07 +0200)]
line_count fixes
1. implementation does not assume staff centred at zero
2. where used for determining whether something falls on a line,
use Staff_symbol_referencer::on_line or on_staff_line
3. where used for determining whether something is within staff or not,
use Staff_symbol_referencer::staff_span
David Kastrup [Fri, 18 May 2012 16:04:41 +0000 (18:04 +0200)]
Issue 2539: Redocument tweak
This adjusts the documentation of \tweak to take into account
a) EventChord not intervening uncalled for (issue 2240)
b) the ability to specify indirect grobs (issue 2540)
Marc Hohl [Sun, 13 May 2012 20:23:54 +0000 (22:23 +0200)]
Issue 1320: preliminary work - repeat bars defined as context properties
This patch removes the hardcoded bar line types for repeat
constructs; this allows for future changes in the bar line
handling routines without recompiling the sources.
Mike Solomon [Thu, 17 May 2012 06:07:18 +0000 (08:07 +0200)]
Excludes pure neighbors in same column.
This means that, for example, Clef and TimeSignature grobs falling
during the same column will not use each other in pure height
approximations. This allows for tighter horizontal spacing.
PO: modifying po-replace before integrating it to the release process
Until now, updating the translation template file is disconnected from
the releasing process, which means that a dev or translator must
1- run 'po-replace',
2- embed lilypond.pot headers,
3- eliminate all po files that have been moved upwards from po/out to
po/
4- commit the new lilypond.pot
5- run 'make dist' to have a tarball,
6- notify the Free Translation Project where to pick up that tarbal.
The first three steps may already be reduced to one single step by
embedding lilypond.pot directly (with specific options and some 'sed'
when creating) and moving it only in po/, what does this patch.
A second step would be to have a call to po-replace when the Release
Meister enters the dance.
We then will have the same unique tarball to refer, directly from
linuxaudio.
David Kastrup [Wed, 9 May 2012 15:46:05 +0000 (17:46 +0200)]
Issue 2525: Fix a number of display-lily shortcomings
Several postevents including non-shorthand articulations were printed with
redundant direction flag - , command events on single note events were
missing the required direction flag - , and a few other problems.
Benkő Pál [Fri, 11 May 2012 15:50:29 +0000 (17:50 +0200)]
Issue 2515: staff_radius fixes
1. implementation does not assume staff centred at zero
2. where used for determining whether within staff or not,
use new function Staff_symbol_referencer::staff_span instead
David Kastrup [Tue, 8 May 2012 13:30:05 +0000 (15:30 +0200)]
Remove test numbering in display-lily-tests
Numbering the tests made it impossible to extend the tests in logical order
without causing regtest output differences in unrelated output. Failing
tests are now instead flagged using warnings, thus giving accurate
pointers to the problematic line numbers instead of numbers without
conclusive source info. Passing tests with verbose output don't contain
any line number info. This is a prerequisite for extending the test suite
without causing false positives.