* Documentation/user/changing-defaults.itely: fix index for set.
+ * Documentation/user/converters.itely: add convert-ly bugs list
+ from CVS.
+
2004-12-21 Jan Nieuwenhuizen <janneke@gnu.org>
* python/lilylib.py (setup_environment): Set GS_FONTPATH, GS_LIB
Not all language changes are handled. Only one output option can be
specified.
+@ignore
+Copy and paste from CVS, last updated
+Dec 22, 2004
+
+http://savannah.gnu.org/cgi-bin/viewcvs/*checkout*/lilypond/lily-bugs/bugs/convert-ly.txt?rev=HEAD&content-type=text/plain
+@end ignore
+@verbatim
+
+There are a few things that the convert-ly cannot handle. Here's a list of limitations
+that the community has complained about.
+
+This bug report structure has been chosen because convert-ly has a structure that doesn't
+allow to smoothly implement all needed changes. Thus this is just a wishlist, placed
+here for reference.
+
+1.6->2.0:
+ Doesn't always convert figured bass correctly, specifically things like {< >}. Mats' comment on working around this:
+ To be able to run convert-ly
+ on it, I first replaced all occurencies of '{<' to some dummy like '{#'
+ and similarly I replaced '>}' with '&}'. After the conversion, I could
+ then change back from '{ #' to '{ <' and from '& }' to '> }'.
+ Doesn't convert all text markup correctly. Only very simple cases are fixed.
+2.0->2.2:
+ Doesn't handle \partcombine
+ Doesn't do \addlyrics => \lyricsto, this breaks some scores with multiple stanzas.
+2.2->2.4:
+ \turnOff (used in \set Staff.VoltaBracket = \turnOff) is not properly converted.
+@end verbatim
+
+
@node Invoking midi2ly
@section Invoking @command{midi2ly}