From: Jody G. <jod...@gm...> - 2009-01-27 09:04:55
|
Andrea Aime wrote: > Correct. We also have an issue with font height, as we specify > the number we get directly to Font, whose size is not pixels, > whilst SLD size is pixels, generally getting smaller fonts compared > to MapServer which instead follows the spec. That will be another > backward incopatible fix. I think I have already supplied some font height manipulating code in uDig to account for some of these issues (we needed to account for it when working with the printed page where high DPI makes the font height in pixelsapproach look pretty silly. >>> the same result as before. >> I am going to hide behind the SLD specification for a bit; and >> apologize for the earlier mistake. >> however I would like to confirm that non integral widths are allowed. > In our code they are. Schema wise there are no restrictions as > CSSParameter can be anything (mixed mode with embedded expressions). > But yeah, the SDL 1.0 standard says (page 36): > > The “stroke-width” CssParameter element gives the absolute width > (thickness) of a stroke in pixels encoded as a float > > So yeah, it's possible to specify a non integral number. Thanks; I can also make the "default" style for uDig line work to be 0.5 if needed; and add 0.5 to the list of pre-canned options in the combo box. Cheers, Jody |