Hi Chris On 07.07.2010 17:43:31 Chris Lilley wrote: > On Wednesday, July 7, 2010, 4:13:41 PM, Jeremias wrote: > > JM> Those who monitor [email protected] will have seen that I'm > JM> working (among other things) on ICC named color support for FOP and > JM> Batik. I have now a first version that supports cielab() and > JM> icc-named-color() functions from the SVG Color 1.2 Working Draft: > JM> http://www.w3.org/TR/SVGColor12 > > Woohoo, this is great news. Looking forward to playing with that. Also, > its much easier to write test cases when there is a working > implementation to sanity-check them with.
:-) Right, the test cases is also something on my list. Right now, I'm just working off a single A4 page written in XSL-FO that plays through all possibilities in FO and SVG. > > JM> The code relies on changes in XML Graphics Commons which are currently > JM> placed in a dev branch and which are also used by a dev branch for FOP: > JM> https://svn.apache.org/repos/asf/xmlgraphics/commons/branches/Temp_Color > JM> https://svn.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_Color > JM> So adding this to Batik will finally add that dependency on XML Graphics > JM> Commons which we have talked about long ago. > > JM> Adding support for the remaining methods from SVG Color 1.2 won't be all > JM> that hard. There's cielch() that requires a formula to convert the > JM> values to CIE Lab. > > Yes. That's pretty trivial, L is the same and c,h are the polar form of a,b. Right, I've seen that formula somewhere. Should be easy. Some cos() & sin() something. > JM> And finally, the device-specific colors which also > JM> be fairly easy with a little additional work in XML Graphics Commons. > > They are easy to parse, but device-specific colours introduce a > complication in that they are just a recipe for an output device, not a > colour. So they can't be easily combined with other colours (e.g. used > in a gradient, combined using opacity, etc). The sRGB fallback colour > needs to be retained, used if a device-specific colour is mixed with > another colour. I have that mapped already. I just hope XSL-FO 2.0 will do that the same way. http://wiki.apache.org/xmlgraphics/ColorHandling > JM> The question is now, if it were ok, if I created a similar branch for > JM> Batik and upload my changes there for everyone to review. I'm not > JM> technically a Batik committer although I theoretically have write access > JM> to the Batik repo since I'm a PMC member. That's why I'm asking what the > JM> best course of action is. I can also post a patch if that's preferred. > > Personally I would find it easier to check out a branch than to check out a > trunk and then apply a patch each time. > > > -- > Chris Lilley mailto:[email protected] > Technical Director, Interaction Domain > W3C Graphics Activity Lead > Co-Chair, W3C Hypertext CG > Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
