Re: Non-standard Cocoa RTF Unicode encoding?
Re: Non-standard Cocoa RTF Unicode encoding?
- Subject: Re: Non-standard Cocoa RTF Unicode encoding?
- From: Aki Inoue <email@hidden>
- Date: Mon, 8 Jul 2002 03:11:28 -0700
Uli,
Symbol/Dingbats fonts are exceptions here.
And you still have to watch for symbol fonts designed for Windows.
They don't usually have clear mapping to Unicode.
Aki
On 2002.7.7, at 10:45 PM, Uli Zappe wrote:
Am Montag den, 8. Juli 2002, um 05:51, schrieb Aki Inoue:
Still, I have absolutely no idea how I could map the RTF setting
\fcharset80 to one of the encoding constants mentioned there.
Oh, it is indeed an undocumented specification, but it is consistent.
While experimenting further, I have found out that unfortunately it is
not totally consistent.
For instance, if I use the Symbol font, I get:
\f1\ftech\fcharset2 Symbol;
So in this case it's the original Microsoft RTF spec charset value
that's used, and that needs to be translated to
kCFStringEncodingMacSymbol = 33, i.e. by adding 31.
I wonder what's the logic behind that. "If the original charset number
is <77, add 31 instead of substracting 77"??
Directly before the "kCFStringEncodingMacSymbol = 33" entry in
CFStringEncodingExt.h, there is the line
/* The following use script code 0, smRoman */
I wonder if this relates to this problem. If so, there are similar
lines later on, such as
/* The following use script code 4, smArabic */
/* The following use script code 7, smCyrillic */
/* The following use script code 32, smUnimplemented */
What gives??
Bye
Uli
________________________________________________________
Uli Zappe email@hidden
Lorscher Stra_e 5 http://www.ritual.org
D-60489 Frankfurt Fon: +49-700-ULIZAPPE
Germany Fax: +49-700-ZAPPEFAX
________________________________________________________
_______________________________________________
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.