>>>>> On Fri, 25 Mar 2005 16:34:55 +0100, Sébastien Kirche <[EMAIL PROTECTED]> >>>>> said:
>> I suppose no characters in mule-unicode-2500-33ff is accessible >> from QuickDraw Text API that Carbon Emacs is currently using for >> drawing text, at least when using with bundled fonts. > What i can't figure out is that within OSX you can have any unicode > char you want providing that the application is unicode compliant > and that character is accessible at least from the system character > palette. > But for Emacs there is that strange remapping for parts of the > unicode set. So some chars are ok and some not. Quote from "Internationalizing Your Software: File Encodings and Fonts": http://developer.apple.com/documentation/MacOSX/Conceptual/BPInternational/Concepts/FileEncodings.html Carbon and QuickDraw Issues If you have existing QuickDraw code and want to draw text, you should be aware that the QuickDraw Text routines do not directly support Unicode. : The fonts that are installed with Mac OS X have large character sets supporting a wide range of encodings and scripts. For example, Lucida, the system font, supports extended Latin, Greek, Cyrillic, Arabic, Hebrew, and Thai. But if you draw text through QuickDraw Text, you have access only to the MacRoman repertoire. To access the rest, you must use Cocoa or ATSUI. Steven Tamm is working on ATSUI support, and he is planning to add it to the unicode branch. I also think that it is not time to add such a drastic change into the upcoming release version. My change about Central European and Cyrillic display support is a "stopgap" that is intended not to change existing mechanisms. YAMAMOTO Mitsuharu [EMAIL PROTECTED] _______________________________________________ Emacs-devel mailing list Emacs-devel@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-devel
