- From: Alex Danilo <alex@abbra.com>
- Date: Fri, 15 Jan 2010 18:45:09 +1100
- To: Paul Williams <pwilliams@infotrustgroup.com>
- Cc: Helder Magalhães <helder.magalhaes@gmail.com>, "www-svg@w3.org" <www-svg@w3.org>
Opera implements 1.2 Tiny features, I think you'll find it works there. Alex --Original Message--: >Hi Helder, > >Yes, the rub is implementation. To the best of my knowledge, SVG Tiny is not targeted for implementation in any major browser, whereas SVG 1.1 might be. > >~ Paul > >-----Original Message----- >From: Helder Magalhães [mailto:helder.magalhaes@gmail.com] >Sent: Thursday, January 14, 2010 4:39 PM >To: Paul Williams >Cc: www-svg@w3.org >Subject: Re: Minutes, January 14 2010 SVG WG telcon > >Hi Paul, > > >I'm not part of the SVG-WG but here goes (response inline)... > > >> During the discussion of "unit" behavior, I noticed the following: >> >>> ... and there are things that don't have units >>> ... the idea of SVG is it's scalable >> >> Scalable, yes -- but there are cases in which we would like certain elements to be non-scaling -- for instance stroke width and font metrics may want to have non-scaling parameters in the engineering domain. That is, to allow the endpoints of a stroke to expand and contract, but always maintain a particular pixel stroke-width. > >I may be overlooking this but, AFAIK, the non-scaling-stroke >vector-effect [1] (introduced in SVG Tiny 1.2) was specifically >designed for this. :-) > >Please reply with more details if your use-case can't be addressed by >this neat (yet not widely implemented) way to achieve fixed stroke >width. ;-) > > >> Thanks for listening, >> ~ Paul > >Hope this helps, > Helder > > >[1] http://www.w3.org/TR/SVGTiny12/painting.html#VectorEffectProperty > > >
Received on Friday, 15 January 2010 07:46:13 UTC