James Lowe [Fri, 19 Feb 2016 11:54:25 +0000 (11:54 +0000)]
Doc: NR - changing-defaults.itely - various improvements
Issue 4761
A variety of nitpicks and
improvements reported by
Federico Bruni
Some spelling corrections
and typos fixed.
The section on \set vs.
\override has been
edited in an attmpt to
simplify the explanation
for the reader.
Fixed a couple of TODOs.
Added a @c that references
an open issue to improve
the example for pure/unpure
containers as the example no
longer illustrates what it
used to as of LP 2.17.x +
Thomas Morley [Tue, 9 Feb 2016 09:21:00 +0000 (10:21 +0100)]
Issue 4768 Support additional bass strings in TabStaff
- 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.
Simon Albrecht [Tue, 2 Feb 2016 19:38:22 +0000 (19:38 +0000)]
Doc: Updates to CG, Extending, LM and Paper-defaults.ly
Better code formatting in some alists.
Previously, the 110-character lines
made it difficult to read; the new
version is also in line with what
the NR says.
Extending: comment TODO remark Telling
the user that he might be confused about
something (while he doesn’t understand
what exactly that is) only adds to confusion;
Use a properly formatted example;
This should actually show how reformatting
Scheme code makes it easier to read; however,
it uses tabs and the result in both HTML
and PDF is messy.
The new version uses normal spaces only
and should be consistent as well as clear.
Other minor wording and punctuation improvements
Capitalize LilyPond correctly
Fix typo in LM
There was an unmatched parenthesis in the text;
changed into a comma.
Urs Liska [Tue, 19 Jan 2016 09:52:33 +0000 (10:52 +0100)]
#4747: Remove (all) uses of is-absolute?
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.
Urs Liska [Tue, 19 Jan 2016 09:40:13 +0000 (10:40 +0100)]
#4746: Fix is-absolute? on Windows
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.
Issue 4734: Add lilypond-book can use XeTeX backend for auto-detect
lilypond-book uses TeX engine for auto-detect default settings.
In the case of using XeTeX , the detection did not work.
When there is no glyphs, pdfTeX creates PDF.
However, XeTeX does not create PDF.
Threfore, the detection is failed.
If the documents were built by XeTeX,
XeTeX couldn't find picture/pdf/*.pdf for building essay.pdf.
This commit creates symlink to solve the problem.
In the case of pdfTeX, it does not affect.
Do not output CC#7 events in MIDI on dynamic changes
As volume changes for MIDI are encoded as note velocities, it is not
necessary to add "silent" Audio_dynamic elements to Audio_staffs to
be processed by Midi_walker. (Every "silent" Audio_dynamic event
will only get converted to a Midi_dynamic event outputted as a CC#7
event with fixed volume 100 in MIDI, see Midi_dynamic::to_string.
This behavior is not consistent with the handling of other MIDI
controls on which LilyPond will not enforce any "default" values.)
As Staff_performer::get_audio_staff has the side effect of creating
a new Audio_staff for a voice if it does not yet exist, accessing the
current voice's associated Audio_staff was moved before the handling
of Audio_dynamic elements.
Based on the revision history, not emitting any CC#7 events in MIDI
appears to have been the original intention when encoding dynamic
changes as note velocities (93b7a6ff072d73dcdd41da59cd18da8aa8d8e8cb),
but apparently the initial implementation (of passing "silent"
Audio_dynamic events to Midi_walker, and ignoring them only at the
output stage) caused problems with MIDI timing (#1593), possibly
because skipping these events only just before outputting them might
have interfered with the logic for tracking the delta times between
the MIDI events that would be actually outputted. To fix #1593,
commit f114e3c33f9c37c39c7a3fedf66ca5a074785118 conservatively
restored the emission of CC#7 events in MIDI.
The current commit tries to avoid the issues with MIDI timing by
pruning all Audio_dynamic events already from the input given to
Midi_walker, so that Midi_walker sees no events, the skipping of
which would confuse the measurement of delta times at the output
stage.
Simon Albrecht [Mon, 11 Jan 2016 17:40:42 +0000 (17:40 +0000)]
Doc: LM 2.4.1 and NR 3.3.2 additions and corrections
Issue 4721
NR 3.3.2: nitpicks in lily
example; add a missing space;
better code formatting with
\partcombine remove
printPartCombineTexts setting.
Issue 4717
LM 2.4.1: Replace incorrect
naming rule in LM. This
replaces the incorrect rule
about naming variables with a
simple reference to the
'alphabetic-only' _convention_.
A thorough explanation in the
NR remains to be done.
Phil Holmes [Wed, 6 Jan 2016 16:09:50 +0000 (16:09 +0000)]
Document all outside-staff-priority values and neaten table
Follows on from a question on -user.
There aren't that many values
of outside-staff-priority, so it
seems easiest to list them all if
we're going to list most. The
adjustments to the column widths
get rid of unnecessary line wrapping.
Simon Albrecht [Mon, 4 Jan 2016 12:08:05 +0000 (12:08 +0000)]
Store accidental styles in an alist
This rewrites the way how accidental styles
are stored and accessed.
Previously the two were
mangled in the set-accidental-style
procedure so that adding custom styles
required complete redefinition of
this procedure and copying all the
existing definitions. Now, the actual
specifications of accidental styles
are stored in the 'accidental-styles'
alist, and the set-accidentals-properties
and set-accidental-style procedures
have been replaced by a single procedure,
which reads from that alist and
sets the context properties accordingly.
Thomas Morley [Sun, 27 Dec 2015 21:33:12 +0000 (22:33 +0100)]
Issue 4716 Improve note-by-number to deal better with flag-styles
- Per default every ancient note-head will get a mensural-style-flag.
- overriding flag-style will now always work with supported styles:
default, straight- and flat-flags and (neo-)mensural-flags
Masamichi Hosoda [Thu, 24 Dec 2015 15:11:28 +0000 (00:11 +0900)]
Issue 4713/2: Change texi2html option order
To overwrite texi2html default i18n messages with the LilyPond init file,
delete TEXI2HTML_INIT that exists before TEXI2HTML_LANG.
And, add languages minimum initialization before TEXI2HTML_LANG
instead of TEXI2HTML_INIT.
Greg Swinford [Fri, 1 Jan 2016 13:11:35 +0000 (13:11 +0000)]
Doc: LM Single staff Templates - addversion remove
Remove [addversion] from two
snippets that use it. Other
LM templates don't seem to i
nclude \version statements and
[addversion] is adding some
messy extra whitespace in
HTML output.
projects / lilypond.git / log