--- "Andreas L. Delmelle" <[EMAIL PROTECTED]> wrote: > > The XSLT extension functions actually are meant to > redirect certain parts of > the transformation result to other files.
Yes, our properties.xsl used to do that for the 250 or so autogenerated property class files. > In the case such a strategy were used, we may need > to advise our users to > apply certain other rules, like keeping track of the > redirected files Keep in mind, for FOP's xml+xsl->fo->pdf, we don't output an intermediate fo file. So there may be *no* redirected files to keep track of. > (--as > this may be too processor-specific to deal with in > our code) and storing > them in extension elements in the main FO. Err--I'm not sure of what you mean by "main FO"--the redirect mechanism doesn't have a hierarchy--just a series of separate output files. > Our own extension-handling code for the elements in > question should be able > to the rest, maybe in combination with an Ant task. > I'm unsure here--our extensions are just for (additional) formatting objects, perhaps unrelated to how many FO files are being processed. > > Cheers, > > Andreas > Glen (it's apparently "Xalan Week" over here at FOP... ;)
