Re: Normalize an NSAttributedString
Re: Normalize an NSAttributedString
- Subject: Re: Normalize an NSAttributedString
- From: Ken Thomases <email@hidden>
- Date: Sat, 29 Aug 2009 12:22:22 -0500
On Aug 29, 2009, at 11:46 AM, Ross Carter wrote:
Suppose an NSAttributedString comprises the string o + umlaut in
decomposed form, plus one attribute. Its length is 2, and the range
of an attribute is {0, 2}. The string and its attribute are archived
separately as xml data like this:
<string>รถ</string>
<attrName>NSFontAttributeName</attrName>
<attrValue location='0', length='2'>Helvetica 12.0</attrValue>
If, during unarchiving, the string is represented by an NSString
object in precomposed form, its length will be 1, and an attempt to
apply the attribute range of {0, 2} will fail.
But why would it change between archiving and unarchiving?
Regards,
Ken
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please 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