I do not mind, it has the "danger" of making people write non standard SLD
files.
I know the SLD spec says it supports SvgParameters but they only have
examples of hex:
*The “stroke” SvgParameter element gives the solid color that will be used
for a stroke. The color value is RGB-encoded using two hexadecimal digits
per primary-color component, in the order Red, Green, Blue, prefixed with a
hash (#) sign. The hexadecimal digits between A and F may be in either
uppercase or lowercase. For example, full red is encoded as “#ff0000” (with
no quotation marks). If the “stroke” SvgParameter element is absent, the
default color is defined to be black (“#000000”) in the context of the
LineSymbolizer. *
I am sure for SVG based rendering engines they just pass the SvgParameters
through. So I do not see any harm in being more relaxed on parsing.
As for converting to a string, writing out Color.RED as "red", what are
your thoughts?
--
Jody Garnett
On 24 April 2017 at 23:42, Andrea Aime <[email protected]> wrote:
> Wondering if there is an actual need for a function to start with.
> What's the harm in just allowing the CSS color converter to be used as
> normal?
> it would allow named color usage in all styling languages.
>
> Cheers
> Andrea
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
