At 08:51 AM 10/29/01 +0100, you wrote: >I am going to update all the jars in fop to the latest version. I think >they are a bit faster and better and we should keep up to date with what >people are likely to be using. > >I have two questions: > >- do we still need xalan 1.x >I remember there was a reason for supporting this a while back, is this >still the case or can we just use xalan 2.x which has trax. > >- does anyone still need xt support >since this doesn't actually work anymore (and possibly doesn't compile) it >would seem to me that no one is using it and therefore no one needs it >supported.
Our ultimate goal should be no direct dependence on any implementations. Given that JAXP and TrAX and so forth have been out for a while and have support, let's support _those_; that puts the burden where it should be, on the implementations. No vestiges of special-purpose code for Xalan 1.x or XT should remain. The same would apply for fo:instream-foreign-object. We expose an API; if the foreign XML is in namespace 'A', then as long as there is a handler written that understands that namespace, and conforms to our API (essentially, it can generate areas), then all is well. Regards, Arved Sandstrom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
