Cart
[Home] [By Thread] [By Date] [Recent Entries]
Pieter,
At 12:49 PM 11/2/2004, you wrote: Well, it looks like msxsl.exe does make msxml work like it should; you can make it work as if it was Saxon, from the command line at least. Even without that switch you mentioned? Interesting. But I'm most interested in what happens in IE where MSXML is invoked without special arguments. Last I checked, it showed the error. Problem with mxsl.exe is that it shows the output with spaces inserted after each outputted character, which I (carefully) removed in the above output. Don't know why they appear though, and appearently there's no option to just get the output "as-is". That's because it's coming out in UTF-16 (which it is allowed to). Set your output encoding to something else and you won't get those double-wide characters (UTF-8 works fine). Cheers, Wendell
|
