>> -o "D:\htdocs\XML\_benchmark\__TEST__\" "D:\htdocs\XML\_benchmark\"
>> will parse as one argument after the -o option, because the ending
>> quotes for the folders are interpreted as quote-escapes part of the
>> argument due to the preceding backslash (\").
>I think that is the problem Christian.
>On windows, I've never used \ as the separator, always /
>since the interpretation of the separator is done by java, which is wise
>to both formats?
Of course! How didn't I figured THAT out. I've been doing that backslash
escaping for quite a while now (for other purposes I mean). It should have
been obvious. I'll try escaping the backslash itself, but I'm not counting
As for the trailing slash solution, I don't think that would work, because
I'm not always going to use JAVA. I'll also be using the .NET executable,
which I think is interpreted by Windows itself, and Windows is not that
forgiving now, is it? And using file scheme URIs is not a solution, because
then, spaces and other special characters that may occur will be percentage
encoded, and Windows treats percentages specially. If I'll be escaping
something, it better be the backslash.
Anyhow, I think I now have what I believe is the ideal approach. First, no
quotes around all of the paths, as suggested by MK. And also, any spaces
found are quoted. So that the path
Will be turned into
I tested this, and it seems to work... on Windows (with and without JAVA) at
least. Would that cause problems in any other OS' CLI? I'm unable to make
any tests for that myself.
In any way, I now have something to work on. It's only a matter of time
before I test it all and implement it in the big picture.
Thank you all, regards
Vasil Rangelov, out.
P.S. The "big" picture: http://xslt2processor.sourceforge.net