Re: characterAtIndex: method and composite characters
Re: characterAtIndex: method and composite characters
- Subject: Re: characterAtIndex: method and composite characters
- From: "Ewan Delanoy" <email@hidden>
- Date: Sat, 7 Apr 2007 09:40:25 +0200 (CEST)
- Importance: Normal
> In addition to what Doug says, bear in mind that even precomposed
> Unicode cannot be accessed one "unichar" at a time. First, there may
> still be surrogate pairs (two consecutive UTF-16 code units used to
> represent characters beyond the first 16 bits of Unicode), and
> second, there are some characters that cannot be represented by a
> single Unicode code point, even in the canonical precomposed form of
> Unicode (NFC == Normalization Form C). This is because Unicode does
> not contain a precomposed version of the character in question.
>
> Finally, even if there are no individual characters that require
> multiple unichar's, some languages have linguistic units consisting
> of multiple characters that shouldn't be broken apart.
>
> Deborah Goldsmith
> Internationalization, Unicode liaison
> Apple Inc.
> email@hidden
>
Thank you for your remarks. That brings me to a different question : take
a fantasy composed character, not precomposed in Unicode (say, "b" with
a grave accent). Is it nonetheless possible to print it on-screen as a single
character in TextEdit ? If not, is there a simple Objective-C hack that would
allow a Cocoa-based text editor to do that ?
Ewan
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden