> Don't assume a BOM *wouldn't* be in a string, it could well be and its > perfectly legal to do so. You should be able to deal with it either way.
I've never encountered any use of a BOM in a BSTR. Would you ever expect one in a java.lang.String? As it has been, the method would always fail. Now it might fail in a very artificial case. I don't see a justification to keep the patch out. Though a perfect patch could cover the artificial case. There is a problem (maybe it is just Win XP) where relative URI's are not being resolved. Also, I have code that will eliminate the dependency on WININET and URLMON when parsing local files. Way too late tonight, working on the W3C/NIST DOM stuff, maybe tomorrow. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
