| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
The StaffTab notation is a system combining graphic elements of
tablature with standard music notation and Emmett Chapman's finger
symbols for notating tapping on a Chapman Stick.
|
|
|
|
|
|
| |
It is used for setting multiple attributes on <g>
nodes in SVG output, specified as an alist. The id
grob property is no longer used for this.
|
|
|
|
|
|
| |
Deleting music when its 'elements field becomes null? led
to repeat chords disappearing when articulations were
removed.
|
| |
|
|
|
|
| |
Also fixes the look/definition of the high f# saxophone key.
|
|
|
|
| |
Uses it for implementing coord-rotate.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows the `VerticalAxisGroup.remove-layer'
property to accept a list of values. The layer
will stay alive with any other member of the
Keep_alive_together_engrave group with a
remove-layer value in that list.
The principal reason for this patch was to
allow the use of MarkLine contexts in a Frenched
score, where the context should stay alive with
any single staff in a StaffGroup.
This implementation should also allow additional
flexibility with ossia and divisi staves.
|
| |
|
|
|
|
|
| |
This is an oversight from issue 4643
Also extending input/regression/tablature-micro-tone.ly to cover this case.
|
|
|
|
| |
Their presence makes debugging harder by laying false trails.
|
|
|
|
|
| |
This allows to work with ties and glissandi, makes somewhat useful
changes for overrides, changes crescendi to descrescendi and vice versa.
|
|
|
|
|
|
| |
Also changes argument \= to be a key.
Backport-by: David Kastrup <dak@gnu.org>
|
|
|
|
| |
This commit fixes the warning message for OTC fonts.
|
|
|
|
|
| |
This commit adds `close-port` for closing a file
in `scale-down-image`.
|
|
|
|
|
| |
This commit adds `close-port` for closing a file
in `is-collection-fonts?`.
|
|
|
|
|
|
|
|
| |
For multiple output (e.g. `-dbackend=eps`),
conflict checking needs to be done within each output.
Otherwise, the font which is embedded in the prior output
is not embedded in the subsequent output.
|
|
|
|
|
|
| |
This commit adds checking conflicts between fonts
which have same name in 'CFF' table
but different name in 'name' table.
|
|
|
|
|
|
|
|
|
|
| |
`-dgs-load-fonts` loads fonts via Ghostscript.
However, if a TrueType font (TTF)
that does not have glyph names is loaded via Ghostscript,
all characters are shown in TOFU.
This commit lets `-dgs-load-fonts` loads those fonts
in a way that is not via Ghostscript.
|
|
|
|
|
|
|
|
|
|
| |
`-dgs-load-fonts` loads fonts via Ghostscript.
However, Ghostscript could not load
OpenType/CFF Collection (OTC) fonts by this way.
http://bugs.ghostscript.com/show_bug.cgi?id=696808
This commit lets `-dgs-load-fonts` loads the OTC fonts
in a way that is not via Ghostscript.
|
|
|
|
|
|
|
| |
`-dgs-load-fonts` loads fonts via Ghostscript.
However, it could not load the font that has non-zero font-index.
This commit lets it loads the font
in a way that is not via Ghostscript.
|
|
|
|
|
|
| |
This ensures same behaviour of SystemStartSquare while using
RemoveEmptyStaves as SystemStartBar, SystemStartBrace and
SystemStartBracket. The latter ones already have this default.
|
|
|
|
|
|
|
|
|
|
|
|
| |
bar-line::draw-filled-box calls the hereby renamed procedure
bar-line::calc-blot to determine the blot diameter.
It will be used in:
make-simple-bar-line
make-thick-bar-line
make-tick-bar-line
This simplifies user-customized bar-lines, which are build with
ly:round-filled-box.
No need to copy/paste the blot-calculating procedure anymore.
|
| |
|
|
|
|
|
|
|
|
|
| |
This commit adds to distinguish font type
without filename extension,
and to switch font embedding method by font type.
OpenType/CFF Collection (OTC) fonts
which have filename extension `*.ttc' can be used.
|
|
|
|
|
| |
For embedding both PFA and PFB fonts are used
the same procedure `ly:type1->pfa'.
|
| |
|
|
|
|
| |
Example: \displayLilyMusic \time 1,2 3/4
|
|
|
|
|
| |
At the current point of time, their execution only makes sense in the
lily module anyway.
|
|
|
|
|
| |
This concerns pitchnames, default-language, previous-pitchnames,
drumPitchNames, and chordmodifiers.
|
|
|
|
|
| |
This is necessary in order to use session variables
in lily-imports.cc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit adds limited embedding support
for OpenType/CFF Collection (OTC) fonts
which have `*.otc' filename extension.
Essentially, the extension of OTC font files should be `*.otc'.
However, most of the OTC fonts have the extension `*.ttc'
for backward compatibility.
https://www.microsoft.com/typography/otspec/recom.htm
So this is limited support
because most of the OTC fonts cannot be used.
TODO: distinguish files which have extension `*.ttc'
whether TrueType Collection (TTC) fonts or OTC fonts.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts
commit f30a8189adbbeefa2103e2c2e194040f66bc2291
Author: Urs Liska <ul@openlilylib.org>
Date: Tue Jan 19 10:52:33 2016 +0100
#4747: Remove (all) uses of is-absolute?
====================
As discussion revealed the commit message is not true
and indicates a misconception.
(car ly:input-file-line-char-column a-location) does
*not* always return an absolute path, instead this
depends on how the file path has been passed to LilyPond.
As this commit changed the behaviour of point-and-click
in a somewhat unintentional and unmaintainable way it
is better to revert the commit. Especially as the
original behaviour was not harmful.
========================
The check for absolute paths in in output-ps.scm
and -svg.scm is unnecessary because
(car ly:input-file-line-char-column a-location)
always returns an absolute, slashified path
Now is-absolute? is not used anymore by LilyPond itself. (reverted from commit f30a8189adbbeefa2103e2c2e194040f66bc2291)
|
| |
|
|
|
|
|
|
|
|
| |
Putting them as native variables in the parser module (rather than
using export/import) makes `set!' and `define' equivalent rather than
having `define' create a shadowing definition of the session variable.
That is important in order to avoid the values of the variable
diverging between parser module and `lily'.
|
|
|
|
|
|
| |
Lets the user provide a (quoted) function that is used
to determine the list of ledger positions for a given
note head position.
|
|
|
|
|
|
| |
Typical use case is:
\once \override NoteHead.ledger-positions = #'(...)
where the user specifies a list of ledger positions.
|
|
|
|
|
|
|
|
| |
(... for now at least).
This fixes the include-string.ly regtest, and a few others,
that previously could not be compiled when enabling
the -dembed-source-code switch.
|
|
|
|
|
|
|
|
| |
This will likely be changed anyway as soon as rewriting
chord-names is seriously tackled.
At least it might be a reminder to take care of the possibility
a user wants to unset majorSevenSymbol.
Regtest amended.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A key (previously a symbol) can be either a non-negative
integer (obeying the predicate index?) or a symbol. When used for
overrides/reverts, the first elements of a path may not actually be
numbers but they are flagged as an error by other means: since a full
override path can be the concatenation of several key lists, the leading
elements are not treated differently by the list predicates.
Strictly speaking this should not be the case for key-list-or-music? or
key-list-or-symbol? predicates, but making them behave differently seems
unwarranted. Arguably key-list-or-symbol? should possibly be
key-list-or-key? instead.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By using the new -dembed-source-code command line switch,
users may now include their LilyPond source code in the
generated PDF (using the pdfmark EMBED feature); although
the PDF is not modified in any visible way, embedded .ly
files should appear in viewers that support this feature
(other viewers should degrade gracefully).
This patch adds a new ly:source-files function (with
an optional parser arg) that allows to retrieve the list
of (non distribution-provided) ly files involved in
making the current score.
|
|
|
|
|
|
|
| |
French users now have the ability to enter the D pitch
as "ré" instead of Italian-like "re". In addition, the
French input language accepts double sharps entered using
the -x suffix.
|
|
|
|
|
|
| |
if the user has not set the font, use a
meaningful svg default ('serif' 'sans-serif'
or 'monospace') for the font-family property
|
|
|
|
|
|
|
|
|
|
|
|
| |
Issue 4766
This command acts as a
front-end to \with-dimensions,
taking the new dimensions
from a markup object instead of
having them explicitly given.
Also provides a Changes.tely entry.
|
|
|
|
|
|
|
|
|
|
|
| |
- new context-property: additionalBassStrings
- new regtest
- new entries in NR, Changes
Pitches on those additional bass strings will be printed as:
a, /a, //a, ///a, 4, 5 ...
as common for baroque lute, depending on settings for fretLabel and
additionalBassStrings.
|
| |
|
|
|
|
|
|
| |
Issue 4753
In case style is not a symbol.
|
|
|
|
|
|
|
|
|
| |
The check for absolute paths in in output-ps.scm
and -svg.scm is unnecessary because
(car ly:input-file-line-char-column a-location)
always returns an absolute, slashified path
Now is-absolute? is not used anymore by LilyPond itself.
|
|
|
|
|
|
| |
is-absolute? only looked for "?:/" and not for "?:\" to determine
the drive letter on Windows. Therefore
#(display (is-absolute? (ly-getcwd))) erroneously returned #f on Windows.
|
|
|
|
| |
Change regtest /input/regression/markup-line-styles.ly accordingly
|
|
|
|
| |
This avoids ambiguity with bow-height and thickness
|