Carl Sorensen [Sat, 17 Mar 2012 03:17:36 +0000 (21:17 -0600)]
Autobeaming works properly with tuplet recheck (Issue 2408)
When a new shortest duration is added to a beam, the beam is
rechecked for desired division. Prior to this fix, the tuplet
multiplication factor was ignored when calculating the duration
of each note in the beam during the recheck.
Fix potential memory leak in beaming-pattern::end_moment
Mike Solomon [Fri, 23 Mar 2012 08:30:41 +0000 (09:30 +0100)]
Positions TupletNumber correctly when Script and Slur are present.
There was previously a circular dependency that went:
TupletNumber needs TupletBracket position
TupletBracket needs Script position
Script with avoid-slur set to around or outside needs Slur position
Slur needs TupletNumber position
This is avoided by not doing Script vs TupletBracket collision
avoidance for Scripts that (a) are encompassed by a slur; and (b)
have avoid-slur set to outside or around. The worst-case scenario,
then, is the same collision that would have been present before
Slur vs TupletBracket collision avoidance was implemented. A more
thorough solution would be to have an avoid-tuplet-bracket property
that functions like avoid-slur.
James Lowe [Sun, 11 Mar 2012 20:08:21 +0000 (20:08 +0000)]
Doc: NR add predefined paper sizes to appendix
Issue 2391
Copied predefined paper size entries from scm/paper.scm as a seperate
appendix entry in order to better document predefined paper sizes.
Also revamped section on Paper Sizes including better @cindex entries,
reworded explanation and examples including how to create a custom
paper size without the need to edit scm/paper.scm
Added note in scm/paper.scm to say that the appendix entry was not
autogenerated so that any new entries will not be forgotten to be added
in the appendix - until someone 'scripts' it.
Peter Chubb [Thu, 22 Mar 2012 22:45:54 +0000 (22:45 +0000)]
Articulate.ly - Fix Mordents and Pralltriller
Mordents should be on-beat, not grace notes. And pralltrillers
(half-shakes) are always either 4 alternating notes, or an inverted
mordent.
There is of course a general problem here in that the way ornaments
are realised has changed through the centruries. Even Bach and Clementi
disagree! I'm following CPE Bach's 'True art of the Keyboard Playing'
in the interpretation here. To do the job properly we'd have two
articulations: \prall and \inverted_mordent and treat them
separately for MIDI, but typeset the same glyph.
Julien Rioux [Fri, 16 Mar 2012 19:01:14 +0000 (15:01 -0400)]
Remove hard-coded links to v2.13 docs (issue 2399).
ONLY_WEB_VERSION will take the value vMAJOR.MINOR from the top-level
VERSION file. If we ever want to change the online docs to point to
e.g. doc/devel, ONLY_WEB_VERSION should take the value devel.
Marc Hohl [Mon, 12 Mar 2012 07:24:12 +0000 (08:24 +0100)]
Issue 2348: Handling of open strings in tablature
This patch creates a switch called restrainOpenStrings. When set to #f
(default), LilyPond considers using open strings even if the normal fingering
calculation would consider them "out of reach".
Setting restrainOpenStrings to #t makes open strings non-special for
the fret calculation routine.
James Lowe [Sun, 11 Mar 2012 13:45:36 +0000 (13:45 +0000)]
NR: General tidy up - @seealso @knownissue spacing
No new information added. Trying to make @seealso sections follow CG policy
including line breaks for consistent visual layout in *.itely files.
Notation Reference only:
Made sure all existing @seealso entries were
i. In the correct order as per the CG
ii. Each @seealso was labelled correctly (i.e. 'Extending LilyPond'
instead of just 'Extending' - as per CG).
iii. Correct punctuation marks at the end of each line entry
iv. Made line breaks between each section consistent (one line space
after main sections). Kept one line space between @seealso and @knownissues.
Made sure two line breaks before next @node. Any @cindex have line space
either side of entry. Removed line space between @seealso and @knownissues
and their respective text entries.
v. Removed @c sections that contained empty @seealso entries
that were just 'placeholders' for the 'future' - as this isn't
standard practice.
Trevor Daniels [Fri, 9 Mar 2012 17:42:59 +0000 (17:42 +0000)]
Improve auxiliar/doc-section.sh
This is intended to quickly compile a section
of the manuals as a check during doc editing,
but parts of it were broken. This patch returns
it to a usable state.
- fix help
- automatically invoke browser to view output
- add choice of browser
- fix pictures
- re-implement option to delete or retain
temp files
projects / lilypond.git / log