At 09:26 PM 7/27/01, M.-A. DARCHE wrote:
For more information on this, I would suggest to refer to the
* RFC Uniform Resource Identifiers (URI): Generic Syntax
http://www.ietf.org/rfc/rfc2396.txt
* RFC Uniform Resource Locators (URL)
http://www.ietf.org/rfc/rfc1738.txt
Here are some
On 20010727 22:26 (Friday), M.-A. DARCHE wrote:
For more information on this, I would suggest to refer to the
* RFC Uniform Resource Identifiers (URI): Generic Syntax
http://www.ietf.org/rfc/rfc2396.txt
* RFC Uniform Resource Locators (URL)
http://www.ietf.org/rfc/rfc1738.txt
I
* Bradford, Denis:
Bingo! My system ID for the DTD didn't use the file:/// convention at
all.
AFAIK, the convention is not « file:/// » but « file:// ». The third
slash is only required on UNIX systems, in order to denote the root
directory.
Cheerio!
--
Jean-Baptiste Quenot
At 10:01 AM 7/27/01, you wrote:
* Bradford, Denis:
Bingo! My system ID for the DTD didn't use the file:/// convention at
all.
AFAIK, the convention is not « file:/// » but « file:// ». The third
slash is only required on UNIX systems, in order to denote the root
directory.
I'd
Bingo! My system ID for the DTD didn't use the file:/// convention at all.
Thanks so much - this brings us closer to being able to switch from dsssl to
xslt, which we'd much prefer to invest in.
The error I'm working on now is at the end when the toc is autogenerated (we
have no TOC coding in
Bradford, Denis [EMAIL PROTECTED] writes:
Would this also be the cause of the error below?
java com.icl.saxon.StyleSheet xmldiffmrg.xml htmlhelp.xsl
Error
java.net.MalformedURLException: unknown protocol: d
Transformation failed: run-time errors were reported
You're on Windows,
/ jENs [EMAIL PROTECTED] was heard to say:
| Is there a patch available or in the pipeline ?
It's in CVS already, and will be in the next release. You need the
xsl/extensions/saxon643/ files. (Saxon's API seems to change at every
minor revision, sigh.)
Be
