Michael Smith wrote: > > Jirka, you wrote: > > > Paul Grosso wrote: > > > > > I'm getting those problems every time I try to compile htmlhelp.xsl with > > > either one of several versions of Xalan. Has anyone used htmlhelp.xsl > > > successfully with Xalan? > > > > htmlhelp.xsl doesn't work with Xalan as Xalan doesn't support text > > output method on chunks. (At least it didn't supported it last time I > > checked it.) You can try Saxon and xsltproc, they work without problems > > with htmlhelp.xsl and are much more faster than Xalan. > > Is there any possible workaround for this issue -- an > Xalan-specific conditional that could be written into the > stylesheet to get it to work with Xalan -- or maybe a two-stage > process that could be used with Xalan?
There is workaround, but I dislike it as it isn't nice. I will test whether this workaround didn't break Saxon and xsltproc support. > The reason I ask (and the reason I think it might be important to > support Xalan in spite of this current deficiency in its > functionality) is that I know there are some packaged products, > with a installed user base, that use Xalan built-in for doing XSLT > transforms. So moving over the product to using Saxon or xsltproc > would mean updating the whole installed user base. > > Also, I think a lot of the people using these packaged products > are likely to be Windows users, the very ones that would really > benefit from and value having built-in, off-the-shelf support in > the packaged application for generating HTML Help using the > process you've developed. You are right. I will try to solve this issue. Jirka -- ----------------------------------------------------------------- Jirka Kosek e-mail: [EMAIL PROTECTED] http://www.kosek.cz