Not sure if we want break backward compatibility or not. I think the
current implementation is confusing. IF we want to do that,
then better sooner than later.
I would urge against the default = don't work option.
If that's what backward-compatibility would give then backward-compatibility
Hi Dick,
Generally, it is the last import that takes precedence, so putting
outputset.xsl first would not have an effect. The issue with Saxon 6 is
that once the xsl:output doctype attribute values are set to some nonblank
value, they cannot be unset to blank by a later import. As long as
Hi Bob,
Thanks for the information. That explains what was going on, though it seems
more like a Saxon 6 bug than a quirk:-).
I had thought that I was through with epub2, but it turns out that there are
some distributors out there who still only accept epub2, even if your epub3
doesn't do
I figured out a better way to handle this. The HTML stylesheets already
have an internal variable named 'chunk.base.dir' that actually used for
chunking. It originally ensured that the base.dir value had a trailing
slash. I've modified it for epub3 to append the value of $epub.oebps.dir,
