From: fred <fred>
Date: Thu, 12 Dec 1996 12:36:31 +0000 (+0000)
Subject: lilypond-0.0.17
X-Git-Tag: release/1.5.59~6599
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=f102be1ebabcb6e99496960ab725e9a7138555cd;p=lilypond.git

lilypond-0.0.17
---

diff --git a/Documentation/inputformat b/Documentation/inputformat
index e6c0de2261..d82c02b2e5 100644
--- a/Documentation/inputformat
+++ b/Documentation/inputformat
@@ -20,7 +20,6 @@ In musicmode, eg,
 
 	''!c8.-"text"_v
 
-
 a lot of characters parse differently
 than in "command" mode, eg,
 
@@ -47,14 +46,14 @@ not really crystallized; you can use '#' or '%' as line comment
 OTHER
 
 A correctly parsed .ly does not guarantuee output. A lot (most) of the
-checking is done *after* parsing (some checks are after the break calc!)
-I'm sorry.
+checking is done *after* parsing (some checks even are done after the
+break calc!);  I'm sorry.
 
 The parser's job is to construct appropriate objects. It will *only*
 detect parse errors.
 
 LilyPond first reads 'symbol.ini', which contains declarations crucial
-to proper operation of LilyPond (symbol tables)
+to proper operation of LilyPond (symbol tables, note names)
 
 This language looks a lot like Rayce's which in turn owes a lot to the
 POVRay raytracer. Now, I know, musictypesetting and Raytracing do not