David Kastrup [Tue, 23 Oct 2012 05:52:45 +0000 (07:52 +0200)]
Create \temporary for doing overrides without pop-first set
Normal overrides change the top of the current property stack rather
than pushing to it, by having the pop-first property set in the music.
\temporary will remove this property from its argument's overrides.
For property-changing music that is not an override, a warning will be
generated.
Calling \temporary \override and \revert in succession on the same
property will have a net effect of zero. Similarly, pairing
\temporary and \undo on the same music containing overrides will have
a net effect of zero.
In more complex arrangements, \revert will revert to the state before
the last (matching) \temporary override of the same property.
Properties are maintained conceptually using one stack per property
per grob per context. Using \push/\pop instead of \temporary/\undo
was deemed unsuitable for a musician-accessible user interface.
David Kastrup [Mon, 22 Oct 2012 13:39:47 +0000 (15:39 +0200)]
Merge branch 'translation' into staging
Conflicts have been resolved generally by taking the version in
master, with the exception of Documentation/fr/notation/ancient.itely
requiring a more elaborate merge.
Benkő Pál [Fri, 7 Sep 2012 18:51:51 +0000 (20:51 +0200)]
redesign dot placement of repeat sign
refines6239ab9f01fcb31fbd6d5f7e81a98a7f58e663bf in that allow both
dots in the same space only as last resort (for two-line staves or for
exotic staves where all outer spaces are too narrow or asymmetric);
put no lower limit on the space required between dot and staffline.
an important example is TabStaff, which, for the present purposes, is
equivalent to a Staff with line-count 6 and staff-space 1.5.
Benkő Pál [Fri, 7 Sep 2012 17:39:21 +0000 (19:39 +0200)]
new regtests for dots of a repeat sign
- test default tablature
- test set-global-staff-size and layout-set-staff-size combinations
in default and extreme circumstances to make sure that real world
usage is not hindered
David Kastrup [Mon, 24 Sep 2012 09:59:42 +0000 (11:59 +0200)]
Issue 2856: Get along with use of grob-property instead of grob-property-path in overrides
LilyPond uses a willy-nilly mixture of grob-property and
grob-property-path when generating overrides programmatically (the
parser only uses grob-property-path). Several override-reinterpreting
commands and functionalities were not prepared to deal with this.
Add examples of
- connecting notes across staves
- connecting notes in chords
- adding timing marks and expressions to long glissandi
- making glissandi breakable
(Based on original work by
Tiresia GIUNO <tiresiag@googlemail.com>,
a patch by Werner LEMBERG <wl@gnu.org> and
advice from Benkő Pál <benko.pal@gmail.com>)
Trevor Daniels [Wed, 29 Aug 2012 10:13:44 +0000 (11:13 +0100)]
Doc: NR 3.2.1: clarify titles and \header blocks (2652)
- drop use of "title blocks"
- make headings consistent
- explain the two titling areas
- explain the four positions for \header blocks and their
hierarchy
- clarify text in several places
Marc Hohl [Wed, 1 Aug 2012 19:15:46 +0000 (21:15 +0200)]
New bar line interface
* the input string of a bar line called by \bar "<bar string>" resembles the output one-by-one; a repeat sign is called by ":|."
* (define-bar-line ...) or \defineBarLine allows for new definitions. These functions have four arguments, namely
the bar line itself, the bar line used at the end of line, the bar line used at the begin of a new line and the span bar line.
* Annotations for barlines can be added to distinguish between two identical barlines with different break
apperance or span bar lines.
* To align span bars properly, the space character " " has a
special meaning. When it occurs, the width of the resembling glyph in the bar line definition is used.
* New glyphs can be added easily.
* Volta brackets take the bar line dimensions into account.
Julien Rioux [Fri, 5 Oct 2012 22:09:48 +0000 (18:09 -0400)]
convert-ly: Don't update \version when no rule is applied.
Note that this is not the same as what the existing -d
--diff-version-update command does. The behavior of convert-ly is
unchanged when rules are being applied, and -d is still used in the
same way. The change concerns itself only with the case that no rule
applies, because the version of the file is already up-to-date. In
this case, it used to be that the version in the file would be set to
version of the last rule, which would sometimes mean that the version
of the file upon output is lower than the version at input. This is
what we avoid in this patch.
David Kastrup [Wed, 3 Oct 2012 11:38:24 +0000 (13:38 +0200)]
Issue 2874: Provide an \undo function for turning overrides and sets into reverts and unsets
\undo\hideNotes is equivalent to \unHideNotes, \undo\easyHeadsOn to
\easyHeadsOff. While this can't undo reverts, it is useful for a lot
of overriding commands defined in ly/property-init.ly, and is also
useful in combination with \hide/\omit.
Trevor Daniels [Mon, 8 Oct 2012 22:33:49 +0000 (23:33 +0100)]
Doc: improve documentation of Bézier curves (2858)
- add \shape function
- show example of two curves being shaped
- show example of line-broken slur
- show example of S-shaped slur
- relegate setting absolute values to end
and give a more realistic example
- add ref from repeats section for simulating slurs
continuing into alternative blocks
David Kastrup [Mon, 1 Oct 2012 12:15:17 +0000 (14:15 +0200)]
Issue 2872: Provide define-session and define-session-public commands
Also moves the session logic into lily.scm instead of init.ly
A session corresponds to one .ly file on the LilyPond command line;
sessions are supposed to be processed independently in one LilyPond
run.
define-session will declare a variable that has its value recorded at
the start of the first session and reinstated at the start of each
following sessions. This is automatically the case for every variable
defined in variables in the parser module established while loading
ly/declarations-init.ly. However, not every changeable information
handled in the .scm parts of LilyPond can easily or reasonably be
stored in the parser module. define-session (and
define-session-public) provide a way to get the same semantics for
variables defined in the Scheme parts of LilyPond.
David Kastrup [Wed, 26 Sep 2012 13:06:56 +0000 (15:06 +0200)]
Issue 2859: Provide \hide and \omit functions for transparent and void glyphs
Both functions take either a grob name to override, or a music
expression to tweak (that is, the type of the argument decides whether
this results in an override or a tweak).
\hide sets #'transparent for the affected grob to ##t,
\omit sets #'stencil for the affected grob to ##f.
Example uses are
\new Voice \with { \omit StringNumber } { c'\4 }
{ <c' \hide g'~> g' }
projects / lilypond.git / log