Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: loadXML returns XML_E_INVALIDATROOTLEVEL

From: EricC@-----------.---------.---
To: NULL
Date: 12/1/2005 12:23:00 PM
Hi Joe,

Thanks for the reply.  I've dug a little further and the thing that triggers 
it is defining _UNICODE in the C++ headers.  When I switch back to _MBCS, it 
works fine. I know that loadXML only works with UTF-16 text, but isn't ASCII 
a proper subset of UTF-16? The generated XML was created with node->get_xml() 
and written directly to file without modification.

I suppose I have my answer for now. I don't require the _UNICODE define--I 
simply thought I might need it.

Regards


"Joe Fawcett" wrote:

> Given your XML document looks fine I've seen this happen when there is 
> unintentional whitespace at the start of the document.
> 
> 
> -- 
> Joe Fawcett -  XML MVP
> 
> https://mvp.support.microsoft.com/profile=8AA9D5F5-E1C2-44C7-BCE8-8741D22D17A5 
> 
> 
> 


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent