From 5090a5688c0a852a56c689ee2424b9e27c2a657c Mon Sep 17 00:00:00 2001
From: fred <fred>
Date: Tue, 26 Mar 2002 21:46:01 +0000
Subject: [PATCH] lilypond-1.1.20

---
 NEWS | 25 +++++++++++++++++++++++++
 TODO | 44 +++++++++++++++++++++++++++++---------------
 2 files changed, 54 insertions(+), 15 deletions(-)

diff --git a/NEWS b/NEWS
index ed3b41e22c..5df616f269 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,28 @@
+pl 20
+
+
+pl 19.jcn5
+	- interstaff beams v0: see beam-interstaff.ly and wtk1-fugue2.ly
+
+pl 19.jcn4
+	- new stem/beam parameters
+	- bf: forced stem shorten
+
+pl 19.jcn3
+	- dehairification of beam code; cleanup and bugfixes
+	  * stemlength
+	  * forced stem shorten
+	  * slope calculation
+	  * damping and correction
+	  * catch for silly beams: input/test/beam-suspect.ly
+
+pl 19.jcn2
+	- multi-measure-rest is now spanner SkipBars=0 is broken
+
+pl 19.jcn1
+	- hmm, almost centered whole-bar rests -- NOT
+
+********
 pl 18.jcn5
 	- bf: beamtrend
 	- bf: vv-duet
diff --git a/TODO b/TODO
index 8fc5b1d577..f01020231f 100644
--- a/TODO
+++ b/TODO
@@ -6,20 +6,29 @@ done, or is an idea that I want to think about
 
 Most of the items are marked in the code as well, with full explanation. 
 grep for TODO and ugh/ugr/urg
-> I have changed Mark_engraver to use the G_... classes.
-> My implementation has the following shortcomings at the
-> moment.
-> 
-> - markScriptPadding is not supported, since G_staff_side_item does not
->   support padding.
-> 
-> - markBreakPriority is not supported. 
-> 
-> - Mostly, you want the marks aligned with the bar lines. I don't 
->   really understand how to implement that feature.
-> 
-> - You get lots of warnings about missing 'number' and 'Large'
-> 
+
+	> I have changed Mark_engraver to use the G_... classes.
+	> My implementation has the following shortcomings at the
+	> moment.
+	> 
+	> - markScriptPadding is not supported, since G_staff_side_item does not
+	>   support padding.
+	> 
+	> - markBreakPriority is not supported. 
+	> 
+	> - Mostly, you want the marks aligned with the bar lines. I don't 
+	>   really understand how to implement that feature.
+	> 
+	> - You get lots of warnings about missing 'number' and 'Large'
+
+
+	*{  \voiceone <a'4.*2/3  d''4.*2/3 fis''4.*2/3>  [g''8 fis'' e''] d''4 |}
+	 and=20
+	 { \voicetwo  d'4 d'2.*2/3 } spacing
+
+	* tied notes for MIDI
+
+	* sharp /flat on trills (in MIDI ??)
 
 	* scm-ify \property values.
 - The direction of textual scripts ('^' or '_') is ignored.
@@ -30,6 +39,9 @@ grep for TODO and ugh/ugr/urg
 	* update mi2mu for lilypond 1.1
 
 BUGS:
+	* collisions/voices \voiceone \voicetwo are broken; see 
+ 	  input/praeludium-fuga-E.ly
+ 	  mutopia/J.S.Bach/wtk1-fugue2.ly
 
 	* fix: standchen.
 
@@ -573,7 +585,9 @@ SMALLISH PROJECTS
 
 	* handle EOF graciously in error messages.
 
-	* centered whole rest
+	* really centered whole rest
+
+	* centered multi-bar-rest
 
 	* declare notenametab?
 
-- 
2.39.5