Re: NSString and Unicode and Japanese character encodings
Re: NSString and Unicode and Japanese character encodings
- Subject: Re: NSString and Unicode and Japanese character encodings
- From: Izidor Jerebic <email@hidden>
- Date: Thu, 25 Aug 2005 23:14:13 +0200
On Aug 25, 2005, at 10:26 PM, John Stiles wrote:
What actual problem are you experiencing?
There are certainly cases where things do not round-trip in and out
of Unicode and remain bit-identical. This doesn't particularly mean
Unicode is unsuitable as a general-purpose encoding.
Editor program uses internal Unicode representation and reads 'A'
than writes 'B', because conversion from encoding X to Unicode to
encoding X does not preserve 'A' ? How can this be OK?
Maybe these problems are more theoretical than practical even for
Japanese, but Ruby internal string encoding won't be Unicode.
Since my Cocoa application does work with potentially Shift-JIS (or
any supported encoding) encoded files, I wonder what problems it may
encounter and whether I should do something to avoid them. E.g. avoid
using Unicode char extraction/insertion from/to NSString which I use
now, and use purely NSString insertion/extraction, if NSString keeps
internal representation sufficiently rich to avoid problems...
I don't know, that's why I ask...
izidor
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden