Thanks, sorry.. I should have mentioned that I tried just about every namespace trick I could find. I definitely tried binding it to that namespace, even to the fo: namespace, and declaring those namespaces at the top of the document as well as lower.
The only interesting thing is that before I changes out Xalan, Fop was reporting the namespace as null in the log output. After I updated Xalan, the namespace would report correctly as whatever it was for that test... unfortunately, fop would still tell me it didn't have a handler for the svg element. Is there some sort of debug logging that reports the external-element handlers when FOP starts running? Phill -----Original Message----- From: Andreas L Delmelle [mailto:[EMAIL PROTECTED] Sent: Sat 6/10/2006 5:52 AM To: [email protected] Subject: Re: new problem with handling svg elements On Jun 9, 2006, at 19:48, Phillip Tornroth wrote: Hi, > First of all, I'm using 0.20.5 still... I'll switch over as soon as > svg works in the new builds :) > > I started refactoring some of my reports stuff and it took me some > effort to get the Transform class hooked up and working correctly. > Now my xsl/fop transformation is working great, but I've run into a > snag with embedded svg elements. Fop is reporting: > > [ERROR] Unsupported element encountered: svg (Namespace: default). > Source context: unavailable > and > [ERROR] no handler defined for svg foreign xml Try prefixing the svg, i.e. <svg:svg ...><svg:g ...>, and of course bind that prefix to the SVG namespace... I'm not sure whether this is the solution, but I seem to remember this being either a requirement or a recommendation. HTH! Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
