David Kastrup [Thu, 5 Jul 2012 10:24:19 +0000 (12:24 +0200)]
Interpret #... inside of music lists as music instead of ignoring it
One consequence is that you get a warning for things like
\revert Score.BarLine #'space-alist #'cue-clef
which actually reverts the whole of space-alist, then ignores #'cue-clef.
Another is that things like $(set-accidental-style 'dodecaphonic)
can be written as #(set-accidental-style 'dodecaphonic) without
getting ignored in most situations.
Void expressions (like most definitions, or the result of calling
\void) are still silently ignored since they are regarded as
intentional.
David Kastrup [Mon, 2 Jul 2012 18:27:46 +0000 (20:27 +0200)]
Reject \footnote ... \default without grob specification
The behavior of \footnote ... \default without grob specification is,
for most purposes, indistinguishable from user error. In consequence,
it has been turned into user error.
As one consequence, support for the undocumented and inefficient
compatibility mode for use of not-actually-time-based footnotes as an
articulation (-\footnote ... \default) has been removed. This can
occur as the result of convert-ly from older variants of \footnote
syntax. Targetting a NO_SMART conversion error message of convert-ly
for this use case is so much more tricky and error-prone than printing
a warning at run-time that it has not been attempted.
Clean fonts and docs makefiles, trying to fix 'make -j' race conditions
On my machine (GNU/Linux Fedora 17 x86_64 on an Intel Core 2 Duo),
"make -j3 all" repeatedly calls fontforge before needed .pfb files are
generated and makeinfo/extract_texi_filenames/texi2omf before .texi
file has been generated/copied. Fix this by using order prerequisites
and adding targets to WWW-1 (first stage of doc build); order (rather
than ordinary) prerequisites avoid having always outdated targets,
which would trigger compilation at install.
Remove a rule for Info manual that is no longer needed and which might
short-circuit .dep file generation.
mf/GNUmakefile: also factorize prerequisites in fonts using a macro.
Julien Rioux [Tue, 26 Jun 2012 13:54:39 +0000 (09:54 -0400)]
lilypond-book: Remove trailing path separators in include paths.
Remove the trailing path separators ("/" or "\") in include paths
(e.g. "-I ./ -I ../ -I ../common/") as they are not necessary and
cause problems on windows. Solves issue 2623.
David Kastrup [Thu, 14 Jun 2012 11:20:40 +0000 (13:20 +0200)]
Issue 2602: \unfoldRepeats and \repeat tremolo 7,14,15 produces weird output
This just shamelessly copies the logic of make-repeat into unfold-repeats,
on the assumption that we want to have the same rules apply for creating
and unfolding tremoli.
David Kastrup [Mon, 11 Jun 2012 17:28:31 +0000 (19:28 +0200)]
Issue 2598: Allow brackets and parens to start lyrics, disallow "accents"
[] and () are considered as punctuation in lyrics and can start them.
In contrast, "TeX accents" \' \" \` \^ are quite ridiculous to
"support" in lyrics since LilyPond has not been using TeX for a long
time now, so those sequences are no longer considered special in
lyrics.
David Kastrup [Sun, 10 Jun 2012 19:16:00 +0000 (21:16 +0200)]
Protect a few events from gc.
Some may not be related to obscure errors we see, but as far as I can tell,
events don't have built-in protection when sticking around after their
time. I have really no clue how grobs are protected from collection, but
since they do not seem to get extra treatment elsewhere, I hope they'll
be fine until output time.
David Kastrup [Wed, 6 Jun 2012 13:38:23 +0000 (15:38 +0200)]
Issue 2584 (redo 1967): please make partcombine merge slurs
The partcombiner does not really bother about keeping the number of
generated start and end slur events matched, so this attempts to cope
by implementing the following behavior:
a) multiple slur starts on the same moment are not an error but the
same as one.
b) multiple slur ends on the same moment are not an error but the same
as one.
a2) there will be a slur with direction UP if there is at least one
such start event, and there will be a slur with direction DOWN if
there is at least one such end event. This might imply a double
slur, but for ending it, a single slur end is sufficient.
Consequently, a^(_( c)) (the second closing paren not required, just
added for prettiness) will add a double slur.
Anthony Fok [Fri, 8 Jun 2012 11:12:55 +0000 (19:12 +0800)]
Web-zh: Update LilyPond website Chinese translation
This patch brings the LilyPond Chinese (simplified)
website up-to-date, with some revised and added translations,
and old "skeleton files" now filled with actual content.
It should now be fully functional, hopefully, even though
much of the "Chinese" content is still in English for now.
Anthony Fok [Fri, 8 Jun 2012 05:20:47 +0000 (13:20 +0800)]
Web: Add missing <p> in hu, ja, zh versions of "Thanks for hosting"
The Hungarian, Japanese and Chinese translations of the
"Thanks to ... for hosting ..." line were missing an initial
<p> tag that is necessary for keeping text and the
W3C HTML 4.01 validation logo flushed to the right.