I added this to the bug cvs [...]
It would be great if you can store JPG images also which show the
problem!
Werner
___
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
[EMAIL PROTECTED] writes:
I added this to the bug cvs [...]
It would be great if you can store JPG images also which show the
problem!
it's a better idea to use lilypond or lilypond-book to do this, then
we can see what happens to each bugs for every release.
--
Han-Wen Nienhuys
It would be great if you can store JPG images also which show the
problem!
it's a better idea to use lilypond or lilypond-book to do this, then
we can see what happens to each bugs for every release.
But sometimes it is difficult to describe a problem with words. To
compare newer
Werner LEMBERG writes:
But sometimes it is difficult to describe a problem with words. To
compare newer versions of lilypond with the buggy results should be
easier if images are already there...
Yes, a picture showing the bug is a very good idea. That's one of the
reasons why your bug
Microsoft Windows XP ProfessioNnal 2002
Retail price: $270.99 Our low PricHe: $50.00 You Save: $220.00
Adobe PhotoshGop 7.0
Retail price: $609.99 Our low Price: $60.00 You SavRe: $550.00
Microsoft Office XP Professional 2002
Retail price: $579.99 Our low Price: $60.00 You SavIe:
