Re: Converting wchar_t string to NSString
Re: Converting wchar_t string to NSString
- Subject: Re: Converting wchar_t string to NSString
- From: Glen Low <email@hidden>
- Date: Mon, 9 Feb 2004 06:35:12 +0800
No, I do know the difference between encoding and character set. I
thought it was clear from my message that I was using the wchar_t type
(from Panther and Jaguar) and wcs* functions from Panther using a
4-byte (that is what wchar_t is on OS X after all) Unicode character
set. Irrelevant to this discussion but worth noting is that at some
point we intend to provide our own implementations of wcs* functions
so that apps will run on Jaguar and presumably Puma as well. A
wchar_t string in wxWindows is most certainly in the Unicode character
set, now whether it is using UTF-32 or UCS-4 encoding I am unsure,
supporting both would be nice. I will say it's using the wcs*
functions to do all the work so whatever encoding the wcs* functions
are using is what it's using.
Apologies. I was thinking of my Windows experience where sizeof
(wchar_t) == 2, especially since it's only recently that proper wchar_t
support was implemented on OS X where sizeof (wchar_t) == 4. Note that
if wxWindows is using wchar_t from the Windows platform, sizeof
(wchar_t) == 2 and that would be binary incompatible with OS X.
The problem is in all those encodings listed on Apple's page I didn't
see even one that took 4-byte unicode characters in any encoding. Did
I just miss it? I've visited those pages quite a few times.
I took a glance and didn't see any either.
Cheers, Glen Low
---
pixelglow software | simply brilliant stuff
www.pixelglow.com
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.