So, the branch is now created:
https://svn.apache.org/repos/asf/xmlgraphics/batik/branches/svgcolor12

For those who want to give the new functionality a try: I'm fighting a
bit with the whole Class-Path manifest and runtime policy thing. The
easiest thing for me (for the moment) was to do this:

- Compile XML Graphics Commons: 
http://svn.apache.org/repos/asf/xmlgraphics/commons/branches/Temp_Color
- Compile Batik (Target all-jar)
- Copy xmlgraphics-commons.jar (see build directory) to FOP's lib
directory.
- Copy batik-all.jar to FOP's lib directory.
- Compile FOP: 
http://svn.apache.org/repos/asf/xmlgraphics/fop/branches/Temp_Color
- Instead of running Batik's rasterizer, use:

fop.cmd/fop.sh -imagein mysvg.svg -pdf out.pdf

...to convert an SVG to a PDF file. That doesn't require complicated
manifest and policy manipulations. And it allows to test through all of
FOP's supported formats whereas in Batik only PDF is currently available
besides bitmap formats.

I've added a couple of simple test files in samples/tests/spec12/paints/.

On 09.07.2010 16:44:24 Jeremias Maerki wrote:
> On 08.07.2010 11:44:45 thomas.deweese wrote:
> > Hi Jeremias,
> > 
> > Jeremias Maerki <[email protected]> wrote on 07/07/2010 10:13:41 AM:
> > 
> > > Those who monitor [email protected] will have seen that I'm
> > > working (among other things) on ICC named color support for FOP and
> > > Batik. I have now a first version that supports cielab() and
> > > icc-named-color() functions from the SVG Color 1.2 Working Draft:
> > > http://www.w3.org/TR/SVGColor12
> > 
> >         Great work!
> 
> Thanks. :-)
> 
> > > The question is now, if it were ok, if I created a similar branch for
> > > Batik and upload my changes there for everyone to review.
> > 
> >         It is OK with me.
> 
> Great, thanks for your confidence. I'll create the branch on Monday if
> there's no veto until then.
> 
> 
> Jeremias Maerki
> 



Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to