MusicXML: Insert bar number checks into figured bass and chordnames
I also need to make sure that inserting only a barline does not
generate output for figured bass and chord names. Thus, I have to
keep a variable has_relevant_elements in the voice builder....
Implemented it similar to FiguredBass (using its own voice builder).
The duration of a chord is always the duration of the next following
note (MusicXML does not have the concept of duration for a chord...)
John Mandereau [Sun, 6 Apr 2008 06:29:23 +0000 (08:29 +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:
MusicXML: Run an XML check on the the test files and correct XML errors
MusicXML: Implement metronome mark (tempo marks)
John Mandereau [Sun, 6 Apr 2008 06:11:03 +0000 (08:11 +0200)]
Move sections in French and German docs
LM sectioning is now up to date, NR sectioning is not up to date but
at least ssectioning is consistent; a dozen of xrefs are broken in NR
(in both languages), I'll look at this later.
MusicXML supports multiple types of metronome marks:
-) A simple one: note = beats (=> Lilypond \tempo note = beats)
-) note = other note (=> Lilypond has to use markup, no effect on
midi :-((
-) A very advanced and possibly complex one, which uses <metronome-note>.
This is not yet implemented.
Lilypond does not support parenthesized tempo marks, either, so in
this case, I also generate markup, which unfortunately does not have any
effect on midi..
John Mandereau [Sat, 5 Apr 2008 11:49:49 +0000 (13:49 +0200)]
Merge branch 'lilypond/translation' of ssh://jomand@git.sv.gnu.org/srv/git/lilypond
* 'lilypond/translation' of ssh://jomand@git.sv.gnu.org/srv/git/lilypond:
Spell check
Update of Appendix B of NR, tables
Translation of the LilyPond-Book section of the manual
Fix commitishes to make status page reflect reality
Converters
John Mandereau [Sat, 5 Apr 2008 07:49:17 +0000 (09:49 +0200)]
Merge branch 'master' of /home/lilycvs/git/lily/
* 'master' of /home/lilycvs/git/lily/:
Fix build (use proper line feed)
MusicXML: Produce only one output file; optionally use stdin/stdout
Fix build (files used wrong CRLF vs. CR vs. LF, so lilypond barfed and exited)
More @ref{}.
Rename @refs{}.
Update from Valentin.
Update \parenthesis instructions.
Added @seealso IR refs in NR1.7 Editorial
Added @seealso IR refs in NR1.1 Pitches
MusicXML: Convert <eyeglasses> to lilypond
John Mandereau [Sat, 5 Apr 2008 07:46:51 +0000 (09:46 +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:
Fix build (use proper line feed)
MusicXML: Produce only one output file; optionally use stdin/stdout
Fix build (files used wrong CRLF vs. CR vs. LF, so lilypond barfed and exited)
More @ref{}.
Rename @refs{}.
Update from Valentin.
Update \parenthesis instructions.
Added @seealso IR refs in NR1.7 Editorial
Added @seealso IR refs in NR1.1 Pitches
MusicXML: Convert <eyeglasses> to lilypond
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=-).
John Mandereau [Thu, 3 Apr 2008 16:38:12 +0000 (18:38 +0200)]
Merge branch 'master' of /home/lilycvs/git/lily/
* 'master' of /home/lilycvs/git/lily/:
Removed an useless subsection in the docs
Fix for renamed snippet.
LSR: update.
Proofreading from Neil, thanks!
MusicXML: Fix parentheses with figured bass (code and test file was wrong :( )
MusicXML: Update test files description
MusicXML: Remove executable flag from test file
MusicXML: Include figured bass in the score; simplify test file
MusicXML: Fix typo, remove debug output
MusicXML: Add test file for figured bass
MusicXML: Add basic support for figured bass
John Mandereau [Thu, 3 Apr 2008 16:34:56 +0000 (18:34 +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:
Removed an useless subsection in the docs
Fix for renamed snippet.
LSR: update.
Proofreading from Neil, thanks!
MusicXML: Fix parentheses with figured bass (code and test file was wrong :( )
MusicXML: Update test files description
MusicXML: Remove executable flag from test file
MusicXML: Include figured bass in the score; simplify test file
MusicXML: Fix typo, remove debug output
MusicXML: Add test file for figured bass
MusicXML: Add basic support for figured bass
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.
John Mandereau [Wed, 2 Apr 2008 20:09:32 +0000 (22:09 +0200)]
Merge branch 'master' of /home/lilycvs/git/lily/
* 'master' of /home/lilycvs/git/lily/:
Update from Ralph.
Use now-added snippets.
LSR: update.
Update from Valentin.
compile fix.
Fixes for renamed LSR snippets.
LSR: update.
Removed a number of engravers from the definition DrumVoice
John Mandereau [Wed, 2 Apr 2008 19:52:33 +0000 (21:52 +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:
Update from Ralph.
Use now-added snippets.
LSR: update.
Update from Valentin.
compile fix.
Fixes for renamed LSR snippets.
LSR: update.
Removed a number of engravers from the definition DrumVoice
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 07:14:00 +0000 (09:14 +0200)]
Merge branch 'lilypond/translation'
* lilypond/translation:
Backslash macro
Updates, macros, capitalisation
Spell check and other improvements
Sort of cacophony relief, thanks to Trevor
Repeatd paragraph in Spanish docs
Two final sections from the LM
PO update
Moving objects
Further tweaking and other sources of information
Real music example
Full PO update
PO improvement
Fixing Overlapping Notation
Placement of objects
Fix cross refs
Typo
Fix bad objects message
Appearance of objects
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)