Please type this up in Bugzilla so we don't forget it.
(http://xml.apache.org/fop/bugs.html)--Also include
this sample as an attachment to the bug.  No time
guarantees can be given, however.

In the meantime, Thomas, I don't think I can just
switch our SVGElementMapping implementation from
SVGDOMImplementation to ExtensibleSVGDOMImplementation

because the namespaces are different.  I'll need to
add another ElementMapping to production and

*But*, as you can see in our SVGElementMapping
implementation, we rely on a constant

File below:

To facilitate this change, could you create a
similar--of whatever name--namespace constant in your
ExtensibleSVGDOMImplementation class--probably it
should be "http://xml.apache.org/batik/ext";.


--- Jay Chiu <[EMAIL PROTECTED]> wrote:
> Attached please find a sample fo file with embedded
> svg object.
> You may also take a look at the batik samples,
> xml-batik/samples/extensions/flow/flowtext.svg
> FOP does support the base SVG 1.1 funcationality as
> Batik
> supports. But SVG 1.1 does not support more flexible
> text
> feature, such as text can not wrap onto multiple
> lines. 

--- Thomas DeWeese <[EMAIL PROTECTED]> wrote:
> I have to have a
> different root document
> > for all the batik extension elements, otherwise
> the system uses
> > SVGDOMImplementation to create generic DOM
> element.
>    It sounds like you want to make a small change so
> FOP uses the
> ExensibleSVGDOMImplementation instead of
> SVGDOMImplementation for all
> the elements.

Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software

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

Reply via email to