Thomas DeWeese: > The short answer is that I think that most of the 'old' Graphics > methods that > draw 'lines' should probably include the .5 pixel shift in device space.
But that depends on the current transform, right (because it's device space you're worrying about)? Since I'm just statically converting to SVG, I can't be changing the values every time the transform to device space changes because of panning, etc. > Actually I think the proper hint is shape-rendering="crispEdges", > geometricPrecision indicates that you want the rendering to be as > close to the real geometry as possible (i.e. use anti-aliasing). So actually, I want the converted shapes to use whatever rendering mode is desired from the parent SVG document the HTML is embedded in. For these simple borders, I want them to look right regardless of the rendering mode in use (and ignore whatever rendering hints were set on the SVGGraphics2D). I think this HTML renderer uses only the "old" drawing methods, and assumes pixel level operations (except for anti-aliased text). Is there some way I can get consistent results regardless of the rendering mode? Would it help if I convert all the drawLine calls into a path that covers the same space as the line? > I was under the impression that we already did look at the > rendering hints and set the SVG hints appropriately. Yes it does. -- Cameron McCormack ICQ: 26955922 cam (at) mcc.id.au MSN: cam (at) mcc.id.au http://mcc.id.au/ JBR: heycam (at) jabber.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
