Re: NSStringEncoding -> NSCharacterSet?
Re: NSStringEncoding -> NSCharacterSet?
- Subject: Re: NSStringEncoding -> NSCharacterSet?
- From: Dan Wood <email@hidden>
- Date: Wed, 18 Jan 2006 11:50:35 -0800
Alas, not all users want their pages encoded this way ... Japanese
users, for example, where UTF-8 is not efficient, and ASCII + encoded
entities is not very searchable, and really inefficient.
On Jan 18, 2006, at 11:32 AM, Clark Cox wrote:
2006/1/18, Dan Wood <email@hidden>:
I'm looking for some inspiration on how to figure out the
NSCharacterSet of characters "covered" by a particular
NSStringEncoding. (Or the Core Foundation equivalents,
CFStringEncoding and CFCharacterSet).
For instance, something that would map:
NSASCIIStringEncoding to the character set of 0..127,
NSISOLatin1StringEncoding to 0....255 (I think)
NSWindowsCP1251StringEncoding to the set unicode cyrillic
characters,
NSShiftJISStringEncoding to the set of Japanese characters,
etc.
I am looking for this information so that I can take an arbitrary
unicode string, destined for conversion to HTML, and know which
characters do *not* fit in the specified NSStringEncoding, as those
that need to be 'escaped' (like {).
I can't think of any API to do this, but if you're generating HTML,
why not just either:
- Use ASCII, and encode everything else as a character entity
- Use UTF-8, then you only have to encode special HTML characters
such as '<'
_______________________________________________
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