RE: XMLCh endianness and conversion issues

[da...@us.ibm.com]

> Thanks for the necessary clarification here, I never worked with Unicode 
on
> this level before.
> 
> > A trivial transcoder would simply assign each ASCII character to a 
wide 
> > character (XMLCh).
> 
> Alright. I know that in UTF-8, the ASCII sequences convert to 
themselves.
> By this you must be stating the same is true of UTF-16 / XMLCh?
> And, by my understanding, this trivial routine will be endian safe, 
right?
> It seems that the assignment operation itself will apply the assignment
> properly.

Yes.  See:

http://www.unicode.org/faq/utf_bom.html

> <DON_FIREPROOF_SUIT>
> Also, the coding style of the examples is not very traditionally C++ in 
my
> opinion and is hard to read at least for me, and I prefer to use getopt
> instead of the hand-coded argument acceptance functions used by the
> libraries.
> </DON_FIREPROOF_SUIT>

getopt(s) is not portable to all of the platforms Xerces-C supports, so 
it's not used.

Dave

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org