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.
Urs Liska [Wed, 23 Dec 2015 21:07:22 +0000 (22:07 +0100)]
4704: Improve beam subdivision beaming count
Calculates the remaining length of a beam.
If this is shorter than the regular value at the
subdivision point more beams are used.
(Example: subdivision at 1/8 -> one beam left.
Remaing notes on the beam: 3/32 -> two beams left.)
However, if only one stem is left after the subdivision
this isn't applied in order to have a visual separation.
In this case the default subdivision beam count is used.
Knut Petersen [Tue, 22 Dec 2015 09:10:50 +0000 (09:10 +0000)]
Dont emit \space glyph as empty page number
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".
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.
David Kastrup [Wed, 9 Dec 2015 18:35:45 +0000 (19:35 +0100)]
Issue 4702/2: Add conversion function creator make-semitone->pitch
Also contains a function shift-semitone->pitch for moving a given
conversion function to a different key.
The functions work on semitones rather than the whole tones that
LilyPond uses in the accidentals of its pitches since the semitones
are the more natural basis for most applications (including
Midi-related work) as well as for humans: 6 whole notes per octave
sounds a lot less common than 12 semitones.
There are currently no uses of those functions: they are provided as a
convenience.
Federico Bruni [Sun, 27 Dec 2015 00:05:04 +0000 (01:05 +0100)]
Doc-it: update @ruser links and fix a wrong translation.
Translated the last missing @rweb and @rlearning links.
All @ruser links are translated except for a few links to chapter 2 and
5 of NR in the Learning manual.
Thomas Morley [Sun, 6 Dec 2015 17:52:04 +0000 (18:52 +0100)]
Improve markup->string
issue 4685
Search and filter lily-module for all relevant markup-(list)-commands
to prevent error-prone manual selecting.
Special-casing put-adjacent and fill-with-pattern
markup-commands listed in markup-commands-to-ignore are not taken into
account
David Kastrup [Wed, 9 Dec 2015 20:33:00 +0000 (21:33 +0100)]
Issue 4687/1: Let \etc in partial markup commands stand for any arguments
Previously, \etc could only stand for a final markup argument. Now an
arbitrary kind and number of arguments from the last markup command in
a markup command chain may be omitted.
David Kastrup [Wed, 25 Nov 2015 12:19:26 +0000 (13:19 +0100)]
Issue 4671: convert-ly rule for ly:music-function-extract
The extracted music function no longer takes parser/location arguments since
version 2.19.22. This convert-ly rule caters with the simplest use of
ly:music-function-extract, calling one music function from inside another.
Federico Bruni [Thu, 26 Nov 2015 16:46:42 +0000 (17:46 +0100)]
Doc-it: add chapter 3 of Notation Reference
I left one paragraph of NR 3.6.1 untranslated, as it was
not clear. I'll wait for a doc patch:
https://lists.gnu.org/archive/html/lilypond-user/2015-12/msg00141.html
David Kastrup [Sun, 14 Jun 2015 15:43:13 +0000 (17:43 +0200)]
Issue 4674: Disallow "Scheme_engraver" as an engraver class of its own
It should not be registered as "Scheme_engraver", and no instances of it
should be allowed to exist without a definition of their own.
Also, instead of TRANSLATOR_DECLARATIONS_NO_LISTENER we use
TRANSLATOR_FAMILY_DECLARATIONS for anything not pertaining to an
individually documented translator.
James Lowe [Sat, 21 Nov 2015 21:47:47 +0000 (21:47 +0000)]
Doc - CG: Update information about git-cl
I have moved the information
about how to download and
configure git-cl - that was
previously under the
'Commits and Patches' section -
to its own @node (along side
LilyDev and lily-git) under
the 'quick start' section as
it seemed unnecessarily hard
to find in amongst all the
other information, especially
for new developers.
I've added more explicit steps
for LilyDev users - on how to
update git-cl - and also, more
generally, on how to 'configure'
git cl, especially now that we
are using Allura and need the
extra login/bearer token
requirements.
Thomas Morley [Tue, 3 Nov 2015 21:05:50 +0000 (22:05 +0100)]
Implement make-bow-stencil, make-tie-stencil for use in markup-commands
undertie and overtie
issue 3088
In a follow up it is planned to replace make-parenthesis-stencil with
an appropriate setting of make-bow-stencil and to partially rework the
parenthesize-markup-command
David Kastrup [Fri, 13 Nov 2015 16:54:46 +0000 (17:54 +0100)]
Issue 4657: Tweak Rest.staff-position fails with beam
The problem here appears to be that Beam::rest-collision-callback
returned 0 instead of any previously established offset when it
decided not to tamper with the default rest positioning without beam.
This also rewrites Beam::pure-rest-collision-callback (which appears
to have dealt correctly with the offsets here and appears
disconcertingly diverged from the unpure callback) a bit.
Thomas Morley [Sun, 8 Nov 2015 22:32:32 +0000 (23:32 +0100)]
make supportNonIntegerFret a context-property
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
James Lowe [Wed, 11 Nov 2015 18:17:13 +0000 (18:17 +0000)]
Doc: NR Clarify repeats w\ partials and barchecks
Suggestions from Keith via another
unrelated patch (but in the same
*.itely file) to tidy up the two
examples when not to use bar checks
and partials with \alternative repeats.