+2005-04-22 Bernard Hurley <bernard@fong-hurley.org.uk>
+
+ * scm/x11-color.scm: new file
+ All x11 color names can be accessed with:
+ #(x11-color 'ColorName),
+ #(x11-color "ColorName") or:
+ #(x11-color "color name")
+ If the x11 color name is not recognised then it defaults
+ to black
+
+ * scm/lily.scm: amended to call scm/x11-color.scm
+
+2005-04-24 Han-Wen Nienhuys <hanwen@xs4all.nl>
+
+ * Documentation/user/invoking.itely (Reporting bugs): comment out
+ reference to online PNG bug repository.
+
2005-04-21 Jan Nieuwenhuizen <janneke@gnu.org>
* lily/translator-scheme.cc (ly:translator-property): Remove.
2004-12-09 Graham Percival <gperlist@shaw.ca>
- * Documentation/user/changing-defaults.itely: add info about
- make-dynamic-script
+ * Documentation/user/changing-defaults.itely: add info about
+ make-dynamic-script
- * Documentation/user/notation.itely: add link in dynamics to
- section about make-dynamic-script.
+ * Documentation/user/notation.itely: add link in dynamics to
+ section about make-dynamic-script.
2004-12-09 Christian hitz <chhitz@gmx.net>
foo= \new Staff ..
<< \foo \foo >>
- produce 2 staves.
+ produce 2 staves.
* scm/define-music-properties.scm (all-music-properties): add
2004-11-24 Erik Sandberg <ersa9195@student.uu.se>
- * buildscripts/guile-gnome.sh: Fixed typo.
+ * buildscripts/guile-gnome.sh: Fixed typo.
2004-11-23 Han-Wen Nienhuys <hanwen@xs4all.nl>
2004-11-22 Erik Sandberg <ersa9195@student.uu.se>
- * ly/dynamic-scripts-init.ly: Fixed typo.
+ * ly/dynamic-scripts-init.ly: Fixed typo.
2004-11-22 Han-Wen Nienhuys <hanwen@xs4all.nl>
2004-11-04 Heikki Junes <hjunes@cc.hut.fi>
- * Documentation/user/lilypond.tely: changes 2.3.x to 2.5.x.
+ * Documentation/user/lilypond.tely: changes 2.3.x to 2.5.x.
2004-11-04 Jan Nieuwenhuizen <janneke@gnu.org>
--include-css=.../texinfo.css; command includes css into the html.
* Documentation/texinfo.css: add file.
- define <hr> as black and thin.
+ define <hr> as black and thin.
2004-06-20 Han-Wen Nienhuys <hanwen@xs4all.nl>
@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.
+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.
+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:
problem. Don't forget to tell which version of LilyPond you use! Send
the report to @email{bug-lilypond@@gnu.org}.
+@ignore
+@c the bug database is not up to date enough.
+
When you've found a bug, have a look at our
@uref{http://@/lilypond@/.org/@/doc/@/v2.5/@/bugs/,bug database} to see if
it has already been reported. You could also try to do a few searches
on the mailing list for the bug. Sometimes the bug will have already
been reported and a fix or workaround is already known.
+@end ignore
Here is an example of a good bug report:
if (pc != il->get_column ())
{
/* this shouldn't happen, but let's continue anyway. */
- programming_error (_ ("Separation_item: I've been drinking too much"));
+ programming_error ("Separation_item: I've been drinking too much");
continue; /*UGH UGH*/
}
if (pc != il->get_column ())
{
/* this shouldn't happen, but let's continue anyway. */
- programming_error (_ ("Separation_item: I've been drinking too much"));
+ programming_error ("Separation_item: I've been drinking too much");
continue; /*UGH UGH*/
}