MusicXML: Produce only one output file; optionally use stdin/stdout
-) So far, I generated a file.ly for the score and file-defs.ly for the
definitions. Actually, I don't see why this should be neccessary / useful
as it only clutters the outdir, breaks the links in the examples, makes
the use of stdout (for piping MusicXML through) impossible etc.
So, from now on, only one file (file.ly) will be generated, which contains
all lilypond code from the conversion.
-) Also implemented reading from stdin (if filename is -) and writing to
stdout (if --out=-).
The figured bass definitionis correctly generated and written to the -defs.ly
file, but not yet integrated into the score itself.
For this, I'm keeping a second voice builder while going through the voices'
children and insert the figured bass there and at the end extract the
definition from it.
Removed a number of engravers from the definition DrumVoice
that appeared twice, since they were already inherited from Voice.
Fixes duplicated MultiMeasureRestText entries, for example.
John Mandereau [Tue, 1 Apr 2008 06:48:29 +0000 (08:48 +0200)]
Merge branch 'master' of ssh://jomand@git.sv.gnu.org/srv/git/lilypond
* 'master' of ssh://jomand@git.sv.gnu.org/srv/git/lilypond: (21 commits)
typo
Documentation: Add the @bs{} macro for backslashes in warnings
Minor reminder.
Move "new dynamic marks" into expressive.
Another @ref fix.
Update @node names.
Update from Valentin.
Typo.
Style update.
Removed CVG-ness in docs for Graham :)
Update from Kurt.
Update with GDP info.
Snippets update from Neil Puttock, thanks!
Documentation: Fix cross reference names in PDF generation of the docs
Another compile fix.
Compile fix.
Add reminder for parenthesis.
Update from Valentin.
Strip pathnames from filenames inserted into PFB font names.
Update lilypond-book flag name in lilypond-vars.make too.
...
Documentation: Add the @bs{} macro for backslashes in warnings
-) @bs{} to produce backslashes in warnings (which are now also
correctly converted to a single backslash in pdf
-) Update writing-texinfo.txt accordingly
-) Adjust the one place in the tutorial that caused problems
John Mandereau [Mon, 31 Mar 2008 13:35:27 +0000 (15:35 +0200)]
Elaborate Git instructions for translators
* better instructions for cloning the repository in first place: make
distinction between remote tracking branches and local branches, and
setting up remote for less typing when pulling;
* instructions on how to deal with several branches.
This anticipates the amount of extra Git knowledge that translators
will need when 2.12 comes out.
Documentation: Fix cross reference names in PDF generation of the docs
For cross-references to other documents, one should always use the
five-argument version of @ref (where the fifth argument is the displayed
name of the other document). There won't be a reference to a particular
page, only to the section given by the node name and the name of the
other manual.
Graham Percival [Sun, 30 Mar 2008 17:44:25 +0000 (10:44 -0700)]
Another compile fix.
(sorry, I thought it was all building correctly, but the script
didn't stop when it encountered an error, so the last hundred
lines of the script output still looked good)
Fix parenthesize to work with single notes, rests and whole chords
By default, Lilypond's \parenthesize function (to put parentheses around notes,
articulations, etc.) only works on notes if they are written inside a chord.
In particular, \parenthesize c4 will not work, only <\parenthesize c>4 will.
Similarly, trying to parenthesize a rest will fail. The reason is that
internally, Lilypond understands c4 as <c>4, so the first example is
internally the same as \parenthesize <c>4. The apparent solution is to make
\parenthesize apply to all elements inside a chord instead of the chord
itself (which the current implementation does).
In fact, one can simply redefine the \parenthesize function, which sets
the parenthesize property of a music expression to ##t, so that if applied
to a chord, it will set this property for all note and rest children of a
chord. This immediately solves the problem of parenthesizing rests, as well
as allowing the parenthesizing of all notes inside a chord at once. All
other uses of \parenthesize continue working as usual. So, using the
redefinition of \parenthesize from the snippet, finally the following
commands work as expected:
\parenthesize c4-. \parenthesize r4 \parenthesize <c e g>4->
John Mandereau [Wed, 26 Mar 2008 07:13:57 +0000 (08:13 +0100)]
Merge branch 'lilypond/translation'
* lilypond/translation:
The IR guide
A better translation for Figured Bass
Typo
Tweaking methods
Voices and Vocals, Fundamental finished
Explicitly instantiating voices
Hearing Voices
Update of Documentation/po/de.po
Scheme tutorial
Update macro calls
Scores and parts reloaded
Fix Tweaks menu
Tweaks, naming conventions
Tweaks, introduction
Fundamental, finished
Po update
Fix menu
projects / lilypond.git / log