Hi!
I have tested the XSL sheets with Instant Saxon and XSLTproc under
windows/cygwin. Both these took 25-28 minutes to complete to generate
the HTML Help output target of the XSL sheets.
The output size of XSLTproc was slightly bigger, as it added "
as &qout; in the HTML, and the HTML header part also differed.
A more critical thing is interlinked function references. In the
Saxon output, the functions were not linked, in the xsltproc
output, they were... Hm...
I have also checked the class and function pages. Class dir
parameter list looked this way for both versions:
dir {
dir(string directory);
string path ;
string read();
void rewind();
void close();
}
Uhm, this is not what it should look like
I also checked array_keys, and the param list looked like this:
libxslt: array array_keysarray input [, (mixed search_value )
saxon: array array_keys(array input [, mixed search_value )
Interesting, but this is definetly not what I expected to see...
I have a fresh XSL sheet distro, version 1.48, and a fresh
checkout of XSL customizations from CVS (including common.xsl
for example).
I can understand that there were no errors during the generation,
and the generation may be quicker than the DSSSL ones, but as soon
as we won't solve problems in XSL style sheets like the ones above,
switching to XSL ones would only cause a mass for readers, and they
will be unable to find what they are looking for.
BTW. libxslt generated files in the directory where I started
it, with no respect to the XSL defined output dir, ./html
After the discussions yesterday, I decided to try out some simple
cutomizations using the XSL sheets for the new CHM Edition, but
with such output files, the current XSL customization does not
seem to be a good starting point...
Goba
