> 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 m
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Friday, April 29, 2005 12:19 PM
To: c-dev@xerces.apache.org
Subject: Re: XMLCh endianness and conversion issues
>> This leads to the need to make a very simple transcoder from ASCII to
>> UTF-16. Howeve
> Now, the age-old problem, to which I never found a specific answer
> in the list archives, is the following: I am working on a Solaris
> 2.9 UltraSPARC III system with GCC 3.4.3 and my compiler unfortunately
> defines wchar_t as a 32-bit half word (64-bit mode here). Therefore I
> cannot just cas
I am working on writing an extremely simple C++ utility that just performs
schema validation on a document. In the process of doing this, I need to be
able to accept a schema argument on the command line because the path
specified in the document itself is not always correct. To this end, I read
th