Re: Windows Batchfile calling Saxon - Confusion of / a

Michael Kay wrote:
> There are unfortunately many products that accept Windows filenames in
> contexts where the standards mandate a URI. I have been resisting doing
> this, because I think standards conformance should outweigh minor
> convenience. However, I've been dithering a little on this one recently,
> because once everyone breaks a standard in the same way, they establish a
> new de facto standard. 

If it helps you to resist, know that there are others who feel the same way.

In any case, it isn't just about slashes.  The original poster is going
to find that things break again when he tries to process a file with a
space in it (space is " " in filenames and "+" or "%20" in URIs).  And
if there are any characters above U+7F in the filename, well, UTF-8
encoding followed by percent escaping isn't going to be pretty.  XPath
2.0 has some functions to help here, so perhaps it's simplest to fix the
problem in XSLT-land rather than batch-land.