| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
\tweak should only tweak music as of issue 4533, so move the action of
issue 4500 into \propertyTweak's definition instead.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Werner L reported in 2012 that LP
emits a space glyph referencing
the century schoolbook font at the
top of every page.
If you use gs (old and current) or
pdfcrop to crop output with multiple
pages and print-page-number = ##f
there is excessive white space at the
top of even pages.
ghostscript should handle that better
but a recent gs bug report
http://bugs.ghostscript.com/show_bug.cgi?id=696445
was closed as "WONTFIX".
There is a workaround within lilypond:
\paper {
[...]
oddHeaderMarkup = \markup \null
evenHeaderMarkup = \markup \null
}
Changing " " to "" cured the problem
and appears to have no negative side
effects. Bounding boxes are affected
by this patch certainly so will have
effects in situations where snippets
are used by other third party
programs.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
issue 4655
restores the arguments of determine-frets (changed with issue 4643)
to the previous state, changes the code of determine-frets to rely
on the newly created supportNonIntegerFret-context-property
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
issue 4643
micro-tones in TabStaff are now printable. Unless the chosen
string-tuning will allow it, this feature is disabled for
FretBoards.
- changing determine-frets (adding an optional argument) and
fret-number-tablature-format
- adding a regtest with quarter-tone-string-tuning
- documenting it in Documentation/notation/fretted-strings.itely
and Documentation/changes.tely
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
They are now called as \once \partcombine*
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
One music type and concept less to worry about.
Since this tracks the partcombine decisions via context properties,
using one forced partcombine override in one voice will not be cancelled
by another forced partcombine in another.
In the event stream, \once\override is indistinguishable from
\override ... \revert so in order to be able to implement
\once\partcombine ... in one voice, we have to retain any permanent
\partcombineForce in the other.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
After issue 4442, there is no lexical tie of #{...#} to the current parser,
and even before that, with standard parser/location arguments there should
not have been any problems after issue 3153 at the latest.
|
| | |
|
| |
|
|
|
| |
That avoids the gratuitous creation of an intermediate PianoStaff
context when Dynamics are created at top level.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
This changeset updates the articulate.ly script documentation on the supported
articulations with a description of ac:staccatissimoFactor, and adds
ac:portatoFactor for shortening notes marked \portato, and slurred notes marked
\staccato. The default value for ac:portatoFactor is 3/4 (to match the
current default shortening factor for notes marked \portato when not using
articulate.ly).
|
| | |
|
| |
|
|
|
|
|
| |
issue 4554
fixes \with-link
let it look at the first page number of the entire book
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This applies a markup function to all markup music properties matching a
given music property path.
For example,
\new Voice { g'2 c'' }
\addlyrics {
\markupMap LyricEvent.text
\markup \with-color #red \etc
{ Oh yes! }
}
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The problem with letting the generic \tweak command work as an override
is that the tweaking of lyric events becomes awkward since plain lyrics
are hard to distinguish from property names.
This renames the combined tweak/override command into \propertyTweak and
changes all callers requiring the combined functionality to call
\propertyTweak (or its Scheme equivalent) rather than \tweak.
The original issue allowing \tweak to act as an override was issue 2929.
The issue allowing tweaks to function in \lyricmode is issue 2543.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Issue 4530
With the fix for issue 4465 bassStaffProperties and trebleStaffProperties are gone.
This patch reimplements the functionality to set clefs for the staves and offers the
possibility to set another turning-point apart from middle-C.
This is done with optional arguments for \autochange.
Two regtests are added to reflect these possibilities.
Documentation/notation/keyboards.itely is extended accordingly.
Also inserting the usual remarks about license, etc in autochange.scm.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Either because they were never needed or because the resolution
of Issue 4421 (Make music functions callable from Scheme) now
permits their removal.
Note: not all such constructs have been removed, even though their
removal is possible, since in these cases removal would reduce clarity.
Also tidy up conditional clauses.
|
| |
|
|
|
|
|
|
|
|
| |
Something like
{ \once \tweak color #red \tweak font-size 2 NoteHead
<c' e'>2 c'2
}
previously failed to result in having both tweaks register.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The previous music functions `override' and `revert' (intentionally
colliding with the respective keywords) are removed. It would have been
too confusing to have collisions for `set' and `unset' as well which are
just too similar to existing Scheme constructs.
A convert-ly rule for the previous calls override/revert is not
attempted: they have not yet been documented and have been available
only for one unstable version. Whoever happened to use them already is
capable of replacing them.
|
| | |
|
| |
|
|
|
|
|
| |
Rerunning the conversion rule used in issue4442 fixes this issue. This
should have been a showstopper for commands such as \omit and \offset
but it appears that check-grob-path does not mind the spurious argument
at all.
|
| |
|
|
|
|
|
|
|
|
|
| |
Move the \partcombine context state machine from C++ to Scheme and
move the part-specific work into a new Part_combine_part_iterator.
What remains in Part_combine_iterator is multi-measure rest handling.
The part-specific work is now nothing more than changing context at
specified times, which is basically what \autochange does. There are
still some differences, but most of the implementation of both is now
in the common base Change_sequence_iterator.
|
| | |
|
| |
|
|
|
|
| |
Both will now accept a label meeting the number-or-markup? predicate.
Previously, \mark accepted any expression and Mark_engraver dealt only
partly with them.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Contributed by Julia Meihoefer and Oliver Briede:
Our corrections are based on research we did for Julia's Bachelor
Thesis in computer engineering 'Identification, notation and
reproduction of the Great Highland Bagpipe sound' in August 2014.
This change does NOT include any conversion rules for the the
following noteworthy changes:
* remove \gcatcha, \gcatchb ... \gcatche
* rename \dgrip to \bgrip
* rename \dtaor to \btaor
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
It gets an implicit enclosing Staff when nexted in staff-grouping
contexts, so create an implicit Staff around NullVoice at Score level
|
| |
|
|
|
| |
That way, Staff-level overrides like \key, \transposition and others
arrive in the ChordNames context.
|
| | |
|
