- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Tue, 8 Apr 2014 12:35:23 -0700
- To: Tavmjong Bah <tav.w3c@gmail.com>
- Cc: "Smailus, Thomas O" <Thomas.O.Smailus@boeing.com>, Paul LeBeau <paul.lebeau@gmail.com>, "www-svg@w3.org" <www-svg@w3.org>
On Tue, Apr 8, 2014 at 9:00 AM, Tavmjong Bah <tav.w3c@gmail.com> wrote: > On Fri, 2014-04-04 at 20:28 +0000, Smailus, Thomas O wrote: >> Good idea. Just tested it and that made no difference. >> >> I suspect there isn’t even the functionality internally available to >> better handle subsampling raster inside of SVG content; just for PNG. >> That code base would need to be called to produce the subsampled SVG >> raster content before it is painted. >> >> The bitonal PNG still looks super, and the same image embedded as RGB >> color space raster in an SVG looks horrible with a good percentage of >> the line-art pixels now whitespace. > > 'image-rendering' is just a hint to the renderer. I attempted to get > more useful values for this property into SVG but ran up against the > property having been co-opted by CSS in a spec that won't be finished > for a long time. > > http://dev.w3.org/csswg/css-images-4/#the-image-rendering I'm sorry, I don't recall this occurring. Can you point me back to your suggestions? And the speed at which Images 4 advances is solely a function of what implementors want to implement. If there are individual features, like image-rendering, which are being implemented and which people would appreciate being in a higher-maturity-level draft, let me know and I can kick them back to Images 3 (and do a quick LC->CR cycle) as appropriate. Never let concerns over spec levels dictate what you want to do. We can work around anything. ~TJ
Received on Tuesday, 8 April 2014 19:36:10 UTC