release commit

diff --git a/ChangeLog b/ChangeLog
index 133842e9dac7b841f6d3f87db6bfadc74cd76de9..c560072359b5bb3f2009148c21b0dcf7eab2851d 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2002-11-19  Han-Wen Nienhuys  <hanwen@cs.uu.nl>
 
+       * VERSION: 1.7.8 released 
+
        * lily/grob.cc (warning): better robustness fix.
 
 2002-11-19 Juergen Reuter  <reuter@ipd.uka.de>

diff --git a/lily/grob.cc b/lily/grob.cc
index f11e52a4fc588bbc6e94a0059870508b6907acdf..86c7d499d69c1c5d257307e2ad672465adbf4e47 100644 (file)
--- a/lily/grob.cc
+++ b/lily/grob.cc
@@ -826,37 +826,37 @@ ly_grobs2scm (Link_array<Grob> a)
 IMPLEMENT_TYPE_P (Grob, "ly:grob?");
 
 ADD_INTERFACE (Grob, "grob-interface",
-  "In music notation, lots of symbols are related in some way.  You can
-think of music notation as a graph where nodes are formed by the
-symbols, and the arcs by their relations. A grob is a node in that
-graph.  The directed edges in the graph are formed by references to
-other grobs (i.e. pointers).  This big graph of grobs specifies the
-notation problem. The solution of this problem is a description of the
-printout in closed form, i.e. a list of values.  These values are
-Molecules.
-
-All grobs have an X and Y-position on the page.  These X and Y positions
-are stored in a relative format, so they can easily be combined by
-stacking them, hanging one grob to the side of another, and coupling
-them into a grouping-grob.
-
-Each grob has a reference point (a.k.a.  parent): the position of a grob
-is stored relative to that reference point. For example the X-reference
-point of a staccato dot usually is the note head that it applies
-to. When the note head is moved, the staccato dot moves along
-automatically.
-
-A grob is often associated with a symbol, but some grobs do not print
-any symbols. They take care of grouping objects. For example, there is a
-separate grob that stacks staves vertically. The @ref{NoteCollision}
-is also an abstract grob: it only moves around chords, but doesn't print
-anything.
-",
-  "X-offset-callbacks Y-offset-callbacks X-extent-callback molecule cause
-Y-extent-callback molecule-callback extra-offset spacing-procedure
-staff-symbol interfaces dependencies X-extent Y-extent extra-X-extent
-causes meta layer before-line-breaking-callback
-after-line-breaking-callback extra-Y-extent minimum-X-extent
-minimum-Y-extent transparent");
+  "In music notation, lots of symbols are related in some way.  You can\n"
+"think of music notation as a graph where nodes are formed by the\n"
+"symbols, and the arcs by their relations. A grob is a node in that\n"
+"graph.  The directed edges in the graph are formed by references to\n"
+"other grobs (i.e. pointers).  This big graph of grobs specifies the\n"
+"notation problem. The solution of this problem is a description of the\n"
+"printout in closed form, i.e. a list of values.  These values are\n"
+"Molecules.\n"
+"\n"
+"All grobs have an X and Y-position on the page.  These X and Y positions\n"
+"are stored in a relative format, so they can easily be combined by\n"
+"stacking them, hanging one grob to the side of another, and coupling\n"
+"them into a grouping-grob.\n"
+"\n"
+"Each grob has a reference point (a.k.a.  parent): the position of a grob\n"
+"is stored relative to that reference point. For example the X-reference\n"
+"point of a staccato dot usually is the note head that it applies\n"
+"to. When the note head is moved, the staccato dot moves along\n"
+"automatically.\n"
+"\n"
+"A grob is often associated with a symbol, but some grobs do not print\n"
+"any symbols. They take care of grouping objects. For example, there is a\n"
+"separate grob that stacks staves vertically. The @ref{NoteCollision}\n"
+"is also an abstract grob: it only moves around chords, but doesn't print\n"
+"anything.\n"
+,
+  "X-offset-callbacks Y-offset-callbacks X-extent-callback molecule cause "
+"Y-extent-callback molecule-callback extra-offset spacing-procedure "
+"staff-symbol interfaces dependencies X-extent Y-extent extra-X-extent "
+"causes meta layer before-line-breaking-callback "
+"after-line-breaking-callback extra-Y-extent minimum-X-extent "
+"minimum-Y-extent transparent");