Thanks for your input, Cameron. On 02.02.2008 07:48:33 Cameron McCormack wrote: > Andreas Delmelle: > > A question concerning the dependency on DOM Level 3: does FOP > > *itself* ever use any of this functionality, or is it only Batik that > > *possibly* needs this (depending on whether SVG 1.2 is used > > somewhere)? Does Batik require Xalan to work, period? Or does it only > > require Xalan *if* the user wants access to the SVG 1.2 features? > > Yeah, so Batik uses it for only two things: DOM Level 3 XPath > functionality, as Jeremias mentioned (for 1.1 or 1.2 documents) and sXBL > XPath selector syntax, which is only in 1.2 documents. The former is > only needed if those DOM Level 3 XPath functions are called from script. > The latter is hardly used at all, and will have to be reworked to be XBL > 2.0 in the future anyway, which doesn’t use XPath for bindings. > > Does FOP allow documents to run script before being included in the > resulting PDF (like with the -onload switch to the Batik rasteriser)? > If not, then it’ll be completely safe to omit xalan. Leaving it out > should only cause linker problems when such scripts are run, anyway, not > for arbitrary documents.
Unless Batik somehow automatically runs such scripts, no. FOP doesn't initiate the running of any script code. BTW, the current SVG Print 1.2 WD says: "A User Agent for Printing MUST NOT run any script or start any animation in the SVG document." Since FOP is basically a "user agent for printing", I think we can apply this rule to FOP, too, except if we begin to include interactive features in FOP. > We could rework Batik to use recent JAXP XPath functionality if that is > present, or Xalan if that is present, or fail gracefully otherwise. > > -- > Cameron McCormack, http://mcc.id.au/ > xmpp:[EMAIL PROTECTED] ▪ ICQ 26955922 ▪ MSN [EMAIL PROTECTED] Jeremias Maerki
