Svg examples

> Jordi,
>
> I don't think there is. The oxf:svg-converter processor leverages Apache
> Batik, of which we now include version 1.6. You should be able to just
> feed it SVG in its data input, feed the output to the HTTP serializer
> and see what happens ;-)
>
> -Erik
>
> Jordi Amatller wrote:
>> Hi Orbeon,
>>
>>  
>>
>> Is there any examples on how to use oxf:svg-converter
>> oxf:svg-serializer and some documentation about it?
>>
>>  
>>
>> Thanks again!
>>
>> Jordi
>>
>>  
>>
>
>

> FWIW, I have added the following to the epilogue:
>
> <p:when test="/svg:svg">
>      <p:processor name="oxf:svg-converter">
>          <p:input name="config"><config/></p:input>
>          <p:input name="data" href="#xformed-data"/>
>          <p:output name="data" id="converted"/>
>      </p:processor>
>      <p:processor name="oxf:http-serializer">
>          <p:input name="config">
>              <config>
>                  <header>
>                      <name>Cache-Control</name>
>                      <value>post-check=0, pre-check=0</value>
>                  </header>
>              </config>
>          </p:input>
>          <p:input name="data" href="#converted"/>
>      </p:processor>
> </p:when>
>
> This will add default processing through the SVG converter for all SVG
> files sent to the output.
>
> -Erik
>
> Erik Bruchez wrote:
> > Jordi,
> >
> > I don't think there is. The oxf:svg-converter processor leverages Apache
> > Batik, of which we now include version 1.6. You should be able to just
> > feed it SVG in its data input, feed the output to the HTTP serializer
> > and see what happens ;-)
> >
> > -Erik
> >
> > Jordi Amatller wrote:
> >> Hi Orbeon,
> >>
> >>
> >>
> >> Is there any examples on how to use oxf:svg-converter
> >> oxf:svg-serializer and some documentation about it?
> >>
> >>
> >>
> >> Thanks again!
> >>
> >> Jordi

> Erik,
>
> Is this going to cause a problem for those of us that are using Orbeon
> to serve SVG to clients that support it?
>
> I had a look at the code for the svg-converter, and unless I'm
> misreading it, it uses Batik to convert the SVG document into a png
> image. If this is the case, I'll have to make sure to remove this from
> the epilogue and replace it with the custom SVG handling code I'm
> currently using next time I update.
>

> Daniel,
>
> Good point. We have some plans to make the epilogue easily configurable
> through properties. This seems to be the best way to make theme, XHTML
> processing, and other such interesting options in the epilogue easily
> configurable:
>
> http://forge.objectweb.org/tracker/index.php?func=detail&aid=307139&group_id=168&atid=350207
>
> The current idea is to add an XPath function, accessible from XPL, which
> can access configuration properties.
>
> For the SVG part, I have entered this:
>
> http://forge.objectweb.org/tracker/index.php?func=detail&aid=307303&group_id=168&atid=350207
>
> So hopefully this will soon be just one property away.
>
> -Erik