On Fri, Sep 24, 2010 at 06:44:58PM +0100, Phil Holmes wrote: > ----- Original Message ----- From: "Phil Burfitt" > <phil.burf...@talktalk.net> > To: <lilypond-user@gnu.org> > Sent: Friday, September 24, 2010 6:32 PM > Subject: Re: Optimising output for screen. > > > >>Graham Percival wrote .... > >>PS if you want a hint, one of those discussions was in 2007. > > > >Graham, Thanks for the pointer..had a chuckle with the continued > >discussion 2 years later. Pity the solution was never > >accepted/implemented, > > I didn't read this as arriving at a solution.
Yes. It didn't. I forget whether it was in that thread or a different one, but one possibility is to add "shading hints" (I forget the technical term) to the pdf. This has no effect on the printed version, but it tells some screen output programs how to use anti-aliasing for that particular case. Nobody wanted to spend (estimated) 20 hours[1] working on a feature that would have no effect on the printed output. If you desperately want this, we will (of course) examine any patch which adds this feature. Or you could offer a bounty. But it would be a significant amount of work, so a significant bounty might be required. (for the level of programming+lilypond expertise required, I'd say that $100/hour is roughly a fair wage for this contract job) [1] this estimate is based on a skilled developer, like Carl or Patrick. If a Frog wanted to work on this, I'd budget 50-100 hours for the task. Cheers, - Graham _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
