On Tuesday 07 March 2006 18:03, Scott Cantor wrote: > > I believe, if I try hard enough, I can get C++ to convert from one > > encoding to another using features from <locale>, but I'm not sure. I'm > > guessing it would be overly optimistic to expect the assignment operator > > in std::basic_string<> to provide that conversion. > > No chance. That wasn't what I meant, I just meant that you can use them as > is in 16-bit form with std::string if you're willing to accept that some > versions of some compilers won't let you. > > I'm sure you could get <locale> to work, maybe, but noone I know has tried. > > > > The worst part of this is not having string literals, I freely admit. > > > > w_char doesn't work, eh? > > On Windows, yes. Occasionally a few other places. Not on Solaris or Linux.
<shrug> (How) (D|d)oes XMLCh differ from Unicode 16? > Use Unicode, plain and simple. It's the touch points that create the > problems. I set out boldly on that noble path several years back, and I have the scars to prove it. The problem is that the other guy (who makes the widgets, for example) has to provide that support. I'm using Qt (Linux). I have not tried to go between QString and XMLCh. It may turn out to be very clean and efficient. Steven --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
