xerces and UTF-16 encoding

[stil]

hi,

i've got a little problem with encoding in UTF_16.
i create my document, giving him to my writer to write in a string,
when i set an encoding in UTF-8:

DOMWriter* L_poWriter = L_poImplementation->createDOMWriter();
XMLCh* L_poEncoding = XMLString::transcode( "UTF-8" );
L_poWriter->setEncoding(L_poEncoding);

and then write and get the result:

L_poWriter->writeNode(L_poTarget, *P_poNode);

// WARNING
// using reinterpret cast because the other cast didn't work:
// one day, it's will explode
P_rsResult =
string(
reinterpret_cast<const char*>(
L_poTarget->getRawBuffer()
)
);

the resulting string is valid and contains my Xml.
when i do the same except i encode in UTF-16 the resulting string is
empty

is use xerces v.2.4.0-1.7.0
if you have any idea of what append ?

thanks in advance.
stil

 

[Andreas Prilop]

Organization: http://groups.google.com

i've got a little problem with encoding in UTF_16.

You are funny! You are posting over Google's Usenet interface
and Google itself cannot read UTF-16. Most hits from
http://www.google.com/search?q="UTF+1+6"
are webpages encoded in UTF-16, but not recognized by Google.
Go to the "Cached" versions!

Why do you want UTF-16 in the first place? UTF-16 and UTF-32
are no good for markup languages with ASCII markup.
UTF-8 is much better suited for XML and HTML.
http://ppewww.ph.gla.ac.uk/~flavell/charset/checklist.html

 

[Richard Tobin]

the resulting string is valid and contains my Xml.
when i do the same except i encode in UTF-16 the resulting string is
empty

I'm not a C++ programmer, but are you using a char * string to store
your UTF-16 result? If so, it will probably look empty (or just have
one character) because each character will occupy two chars and either
the first of second char will be zero.

-- Richard

 

[stil]

you're correct, when i check the resulting raw buffer, it contains the
value but the translation into a string lost the result as the first
character is a \0.

stil

ps: i'm going to try a wstring, i hope it will be better

Richard Tobin a écrit :