Julien Rioux [Tue, 14 Feb 2012 14:40:28 +0000 (09:40 -0500)]
Build: Fix lilypond-book regtests when dblatex is not found.
When dblatex is not installed, only the docbook .xml files are
created by a `make doc' but not the .pdf files. We need to filter
those .xml files out of the list of collated files, otherwise
lilypond-book thinks that they are musicxml files and fails to
process them through musicxml2ly.
Julien Rioux [Sun, 22 Jan 2012 00:56:25 +0000 (19:56 -0500)]
Build: Run regression tests for lilypond-book (issue 2223).
Re-enable running the regtests in input/regression/lilypond-book.
Fix various typos, clarify what each input file tests for and
how the output should look, and fix the following problems
in input files in input/regression/lilypond-book:
collated-files.tely:
Was linking to the input files rather than the output files
generated by lilypond-book. The input files were thus not
tested individually as it should but as included files.
Fixed in the local GNUmakefile by an explicit rule for
collated-files.list which tracks the output files.
suffix-texi:
Failed, was not being preprocessed by lilypond-book but simply
copied to the output folder. Fixed in the local GNUmakefile by
adding a specific make rule for it.
tex-twocolumn:
Failed, image had full-page width.
Fixed in the input file by moving \twocolumn to the preamble.
Column width detection in the body of the tex document is not
yet implemented.
texinfo-language-detection:
Suspicious, had a weird @lydoctitle popping up.
Fixed in the input file by defining the @lydoctitle macro.
David Kastrup [Sun, 5 Feb 2012 21:28:48 +0000 (22:28 +0100)]
Make #{ c' #} and x=c' create a pitch instead of a NoteEvent
Since the specification of a pitch without a duration in those contexts
makes it somewhat uncomfortable to guess the actually used duration, it
is unlikely that much use of a default duration has been made in those
constructs. In particular #{ c' #} would appear handy.
Carl [Wed, 1 Feb 2012 04:56:19 +0000 (21:56 -0700)]
Fix tuplet subdivision (issue 2243)
Have stem-engraver add information about tuplet-start, so that it can be passed
into beaming-pattern. Then we subdivide only when we're at *both* start of beat
and start of tuplet.
Add generic metafont file, driver files and
file containing code for glyphs.
Modified scripts used in font generation
to include kievan glyphs.
Modified documentation to include Kievan glyphs.
Added KievanVoice and KievanStaff contexts.
Signed-off-by: Aleksandr Andreev <aleksandr.andreev@gmail.com>
Janek Warchoł [Wed, 8 Feb 2012 08:34:06 +0000 (09:34 +0100)]
CG: username isn't shown when pulling using ssh
CG 3.4.10 point 7 mistakenly stated that when you
pull using ssh, git will display
From ssh://@var{user}@@git.sv.gnu.org/srv/git/lilypond
It displays From ssh://git.sv.gnu.org/srv/git/lilypond,
without username.
David Kastrup [Fri, 27 Jan 2012 16:44:18 +0000 (17:44 +0100)]
Reimplement ChordRepetition facility.
Remove basically all configurability. Reduce parser and lexer support
to hardwired minimum. Don't track the last chord in the lexer/parser.
Instead establish it at toplevel-music-functions level if the user has
not already called \chordRepeats to do so himself.
James Lowe [Fri, 6 Jan 2012 19:51:29 +0000 (19:51 +0000)]
Doc: NR Section on Upbeats made clearer
Tracker issue 2189
Created simpler and clearer @lilypond examples.
Used a less complex, more obvious value for \set Timing.measure position
examples and added a specific example after the @knownissue to show
\partial and \set Timing.. being used together (at the beginning and
after the beginning) to help reinforce the point.
Minor cindex changes and linebreak edits as per the CG
Federico Bruni [Sun, 29 Jan 2012 15:36:28 +0000 (16:36 +0100)]
Doc-it: Add Notation Reference (first chapter).
Committishes in texidoc files will be added later, reasons explained here:
http://lilypond-translations.3384276.n2.nabble.com/how-to-handle-snippets-commit-if-you-don-t-have-push-access-td7154772.html
David Kastrup [Sun, 29 Jan 2012 01:43:02 +0000 (02:43 +0100)]
Don't warn for fingerings outside of [1..5]
Since those are used for _fret_ numbering (and also interpreted in this
manner by the tablature engraver), I can't believe that this has not been
fixed long ago.