summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--ChangeLog4
-rw-r--r--Documentation/user/internals.itely2
-rw-r--r--NEWS84
-rw-r--r--mf/parmesan-custodes.mf6
4 files changed, 46 insertions, 50 deletions
diff --git a/ChangeLog b/ChangeLog
index 412337b03b..f028787940 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
2003-07-02 Han-Wen Nienhuys <hanwen@cs.uu.nl>
+ * mf/parmesan-custodes.mf (dir_down): remove _ from glyph names.
+
+ * NEWS: use complete sentences.
+
* Documentation/user/introduction.itely (Example applications):
add note about databases and lilypond-book.
diff --git a/Documentation/user/internals.itely b/Documentation/user/internals.itely
index fc6c4e198b..e9b5aef53f 100644
--- a/Documentation/user/internals.itely
+++ b/Documentation/user/internals.itely
@@ -740,7 +740,7 @@ Music objects and their properties can be accessed and manipulated
directly, through the @code{\apply} mechanism. Scheme functions can
read and write properties using the functions
@code{ly:get-music-property} and @code{ly:set-music-property!}.
-6
+
The syntax for @code{\apply}
@example
\apply #@var{func} @var{music}
diff --git a/NEWS b/NEWS
index ba633a0582..1251131b46 100644
--- a/NEWS
+++ b/NEWS
@@ -1,31 +1,27 @@
New features in 1.8 since 1.6
=============================
-* INPUT
+** There chord entry code has been completely rewritten. It is now
+cleaner and more flexible.
-** Completely rewritten support for chord entry. Cleaner and more flexible.
+** A new syntax has been added for text entry.
-** Text entry is now done in a separate mode, and is more ergonomic
-than the previous Scheme texts.
+This syntax is more friendly than the old mechanism, and it is
+implemented in a more robust and modular way.
** Deeper integration of the input language and Scheme. You can now use
LilyPond identifiers in Scheme, and use Scheme expressions instead of
LilyPond identifiers.
-** Music types cleaned up and Schemified.
+** The internal representation of music has been cleaned up completely
+converted to Scheme data structure. The representation can optionally
+be exported as XML.
-** New syntax for chords:
+** A new syntax has been added for chords:
<< PITCHES >>
-This is in addition to the < MUSICS > syntax for simultaneous
-music. Combined with this is uniform postfix syntax for articulation:
-
- c8-[-( d8-]-)
-
-for a beamed slurred pair of eighth notes.
-
-*NOTE* In version 2.0, this syntax will be changed to
+In version 2.0, this syntax will be changed to
< PITCHES > for chords
@@ -33,73 +29,69 @@ and
\simultaneous { .. } for simultaneous music.
-** User code evaluation during interpreting. Syntax
+** A new uniform postfix syntax for articulation has been introduced.
- \applycontext #SCHEME-FUNCTION
-
-** XML music output.
+A beamed slurred pair of eighth notes can be entered as
-** Friendly chord-name exception entry.
+ c8-[-( d8-]-)
-** Texts can be put on multimeasure rests, eg.
+In version 2.0, postfix syntax will be the only syntax
+available, and the dashes will become optional.
- R1*20^\markup { "GP" }
+** User code may now be executed during interpreting.
+The syntax for this code is
-* OUTPUT
-
-** Preliminary Sodipodi/SVG output
+ \applycontext #SCHEME-FUNCTION
-* NOTATION
+** New algorithms for chord-name formatting have been installed. This
+algorithm can be tuned and has an ergonomic syntax for entering
+exceptions.
+** Texts may now be put on multimeasure rests, eg.
+ R1*20^\markup { "GP" }
** Ancient notation ... ?? ... (Jurgen?)
-** Completely rewritten text formatting support, implemented in a
-completely modular way.
-
-** Chord name formatting completely rewritten.
+** Glissandi can now be printed using the zigzag style.
-** Texts can be added to multimeasure rests
-
-** Zigzagged glissandi
-
-** Cluster support. Syntax:
+** Clusters may now be printed. The syntax is:
NOTE-\startCluster
..
NOTE-\stopCluster
-** Beat grouping indications. Syntax:
+** For irregular meters, beat grouping marks can be printed. The
+syntax for this is
#(set-time-signature 7 8 '(3 2 2))
-** Nested horizontal brackets for music analysis.
+** Nested horizontal brackets for music analysis can now be printed.
NOTE-\startGroup
..
NOTE-\stopGroup
-** Gregorian ligatures.
-
-** Ottava brackets. Syntax: #(set-octavation 1)
+** Ottava brackets are now fully supported as a feature.
+The syntax is
-** Metronome markings.
+ #(set-octavation 1)
-** Horizontal fingerings on chords.
+** Metronome markings are printed when a
+\tempo command is processed.
-** Tuning of various font glyphs
+** Fingerings can be horizontally on chords.
-** Nested percent style repeats
+** The appearance of various glyphs has been fine-tuned
-* OTHER
+** Different types of percent style repeats may now be nested
-** More advanced emacs support
+** The emacs support has been extended.
-** Completely revised manual, tutorial, and examples section
+** The manual has been completely revised and extended manual.
diff --git a/mf/parmesan-custodes.mf b/mf/parmesan-custodes.mf
index 047ba69f5c..6c76319957 100644
--- a/mf/parmesan-custodes.mf
+++ b/mf/parmesan-custodes.mf
@@ -229,15 +229,15 @@ def custos_vaticana(expr verbose_name, internal_name, ly_name,
enddef;
% custos vaticana, stem up, between staff lines
-custos_vaticana("Custos Ed. Vat.", "vaticana-u0", "vaticana_u0",
+custos_vaticana("Custos Ed. Vat.", "vaticana-u0", "vaticanau0",
dir_up, between_staff_lines);
% custos vaticana, stem up, on staff line
-custos_vaticana("Custos Ed. Vat.", "vaticana-u1", "vaticana_u1",
+custos_vaticana("Custos Ed. Vat.", "vaticana-u1", "vaticanau1",
dir_up, on_staff_line);
% custos vaticana, stem up, anywhere
-custos_vaticana("Custos Ed. Vat.", "vaticana-u2", "vaticana_u2",
+custos_vaticana("Custos Ed. Vat.", "vaticana-u2", "vaticanau2",
dir_up, anywhere);
% custos vaticana, stem down, between staff lines