This is the mail archive of the xsl-list@mulberrytech.com mailing list .
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Thomas B. Passin wrote:
prevent it. Otherwise, it may be the syntax of the file: URL. Try some of the normal variations, like file:///c:\servers\mserver\ojamc2vpt1_part.xsd file:c:\servers\mserver\ojamc2vpt1_part.xsd file:c:/servers/mserver/ojamc2vpt1_part.xsd There is some ambiguity in the RFC about the exact form of file: URLs, leading to different interpretions, and different processors can require different forms. The form you used works on some processors, but I forget what works with which.
It should be noted that all of the forms above adress different locations. The component separator for file: URLs is "/", not "\". Which actually doesn't matter if the whole stuff is passed down to the OS routines, but still... BTW from within applications, Windows accepts both "/" and "\" as directory separators. Furthermore the last two forms are formally relative URLs (despite being absolute file system paths) and could be accidentally passed to an URI resolver. Bottom line: the original form is preferable in any case and should also work for every major XSL processor. J.Pietschmann XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |