Having a BOM for UTF-16 for Little Endian is required, it can be
present for Big Endian, an if there is no BoM present Big Endian is
assumed. That is what The Unicode Consortium has to say about it
anyway. If there is no BOM there are other suggestions made by the xml
spec to determine various
Can't you load it as a binary resource and pass the binary array cast
to char * to libxml2 instead?
On Wed, Jun 2, 2010 at 9:41 AM, ramsundar_govinda...@dell.com wrote:
Hi,
I know this issue might have been asked a thousand times over, but I am
not able to resolve the issue. My situation
Do you suspect that there are more broken implementation vs.
implementations correctly using xmlCleanupParser? The proposed change
would break correctly implemented systems, but still compile and be
hard to detect. Shouldn't correctly implemented systems be favored
over the broken ones?
For
Hmm ... but this point of view would mean that the whole mechanism for this
function is bad for a shared-lib environment, no matter how it's called.
So I could think of this:
* xmlInitParser() and xmlCleanupParser() get deprecated (via the various
compiler specific attributes)
*
.
Thanks,
James
On Fri, Jun 12, 2009 at 1:24 PM, James Hart beeblebro...@gmail.com wrote:
I am working in an application where there are separate components, in
different threads, that don't know about each other but may need different
global parmaters set. I found the blurb about thread safety
I am working in an application where there are separate components, in
different threads, that don't know about each other but may need different
global parmaters set. I found the blurb about thread safety
http://xmlsoft.org/threads.html, but the documentation about globals
themselves in a thread
will
not ever add the deceleration.
~James
On Tue, Jun 9, 2009 at 3:30 PM, James Hart beeblebro...@gmail.com wrote:
Martin,
Exactly the answer I needed. The xmlSaveTree works great.
~James
On Tue, Jun 9, 2009 at 2:56 PM, Martin (gzlist) gzl...@googlemail.comwrote:
On 09/06/2009, James Hart
I have a use case where I need to treat an xml document as a document
fragment, I won't get into the details of why exactly, but lets make the
assumption it is a valid use case for now.
This is the code I am using to get the string of a document, without the
prolog into a buffer:
Martin,
Exactly the answer I needed. The xmlSaveTree works great.
~James
On Tue, Jun 9, 2009 at 2:56 PM, Martin (gzlist) gzl...@googlemail.comwrote:
On 09/06/2009, James Hart beeblebro...@gmail.com wrote:
I have a use case where I need to treat an xml document as a document
fragment, I
