Strings in figuredBass
When I use \figures <"string" number> in Lilypond 2.2.0, the string is not printed; figured-bass.ly in Regression tests don't work also. It works in Lily 2.0.0. Antonio M. -- / <> \ :==: ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user ___ bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond
mypresent
Только одна неделя уникальных скидок! Все что Вам так нравилось, теперь можно купить дешевле! Можно ли сэкономить покупая мечту? Мы утверждаем: ДА! До 1 мая это возможно! http://www.mypresent.ru
Re: Clef change
> BTW, is there a preferred date format & how do you extract that > easily with CVS? I just take the ChangeLog timestamp which normally is precise enough -- optimally, you should refer to the ChangeLog revision number. Werner ___ bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond
Re: Clef change
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
000 items availpableu. onlNine cheamist's shopr
http://www.valuepillsonline.com?rid=1005 Stock is limited and selling fast, so hurry some items Phentermine Xenical Phendimetrazine Didrex Tenuate Adipex Ionamin Bontril Meridia Carisoprodol Soma Fiorocet Cyclobenzaprine Flexeril Flextra Skelaxin Zanaflex Ambien Sonata Propecia Renova Retin-A Nizoral Vaniqa Valtrex Famvir Zovirax Acyclovir http://www.valuepillsonline.com?rid=1005 ___ bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond
Re: Clef change
> > 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). 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... Werner ___ bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond
Spam/virus filtering [Was: Clef change]
Erik Sandberg writes: > I tried also to attach the .png files to the reports to > bug-lilypond, but they were stripped (as usual). So you will need > CVS access to actually see the PNGs. Would it be possible to exclude > .pngs from the attachment stripping on bug-lilypond? Currently, we have only rather crude mailman (version 2.1.4) filtering options at our disposal. This means, iirc, that we can filter any kind of attachment, but we cannot block/hold an email with specific attachments. Such filters will only strip the attachment, and subscibers will still get all the spam, microsoft worm and virus cruft, but only the text part. That made me, sometime begin of March, add filter rules to hold any multipart/mixed on lilypond-user and bug-lilypond. We should really get better spam/virus filtering, or centralized better options, if possible. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond
