On Monday 26 April 2004 07.43, Werner LEMBERG wrote: > > > It would be great if you can store JPG images also which show the > > > problem! > > > > I use .png instead. > > Yes, of course. A typo of mine. > > > I use the convention that if I submit something as "clef-change.ly", > > I upload clef-change.png demonstrating the problem, if appropriate. > > Thanks, I got them. I ask for yet another refinement: Do a zoom at > the problematic spot and crop the image around the buggy detail > (without using anti-aliasing to have the images as small as possible).
So far I've just used plain lilypond --png for simplicity. I'll do more whenever anything seems unclear. I am minimalistic by nature; I don't enjoy putting effort in producing aesthetically correct bug reports if it isn't necessary. To me it's just an illustration to help pointing out what's wrong. So: If it is a layout bug, and it is not immediately 100% clear from lilypond --png + texidoc what the problem is, then I'll do the work of starting gimp; and I'll probably draw a few red rings & arrows, and crop the image. I'll skip this step if it is too obvious (such as misplaced-octaviation or piano-repeat), but i'll do the work in cases such as grace-accidental-spacing. And is space really an issue? A typical bugreport PNG is 5K, which should take about 1 second to download over a modem; and typically <5 people will download it by modem. And the space consumption is not so crucial really; given that one gigabyte costs less than 1 euro these days (so it takes about 2000 bugreports to reach the cost of 1 cent). > Is `\version x.x.x.' precise enough? Be prepared that I use the date > of the ChangeLog file as the time stamp for a bug report... Most bugs I've added have existed in official releases as well, so \version has been enough. But you're right, there should be a mechanism to be more specific than that. I'd suggest to add timestamp = "..." in \header, when needed. BTW, is there a preferred date format & how do you extract that easily with CVS? Erik _______________________________________________ bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond