A decision was made a while back, which I didn't really agree with, to fix
XMLCh to UTF-16 on all platforms. Partly this was because the DOM committee
chose UTF-16 for its representation. So, if this is not compatible with your
wchar_t, you must transcode all of the data to your local wide string
representation before using it. On NT, the stuff spit out from the parser is
directly useable, since UTF-16 is NT's native representation of Unicode. On
other platforms, you'll have to transcode if they don't do the same.
--------------
Dean Roddey
Software Geek Extraordinaire
Portal, Inc
[EMAIL PROTECTED]
-----Original Message-----
From: Mark A Russell [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 30, 2001 3:25 PM
To: [EMAIL PROTECTED]
Subject: XMLCh & wchar_t conversion on multiple platforms
Is there a way to convert between XMLCh and wchar_t on both the AIX 4.3 &
Solaris platform that won't break my code on NT?
I have some code that I'm trying to port from win32 that uses wchar_t for
unicode support. This code currently makes use of some of the xerces
functions that only take XMLCh 's. An example is shown below:
const wchar_t * szSourceBinding =
attributes.getValue(CBOITagFactory::ATTR_SOURCE_BINDING);
The CBOITagFactory::ATTR_SOURCE_BINDING is simply a wchar_t. (XMLCh's are
currently unsigned shorts)
My requirement is to maintain unicode support on all three platforms. I
thought about just redefining XMLCh's to wchar_t's like they used to be
around 1.2, however after looking at the documentation that seems like a
very bad idea because of an incompatibility that would arise on the Solaris
platform.
Any help would be much appreciated.
btw - What happen to the mailing list archives? They seem to be unreachable.
Mark A Russell
NextGen Software Engineer
CSG Systems, Inc.
E-Mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
