>>>>> On Wed, 21 Sep 2005 09:11:46 -0700 (PDT), Orca <[EMAIL PROTECTED]> said:
> Apparently, a similar bug affects NeoOffice. It appears to be the > result of some change in Mac OS X Tiger's font handling. As with > emacs, NeoOffice handled these font variants properly under Jaguar > and Panther. > <http://bugzilla.neooffice.org/bug.php?op=show&bugid=802&pos=4> A very informative link for me. Thanks a lot. So, my previous post was probably wrong for Panther. Sorry about that. > This issue does not show up in other text editors (SubEthaEdit, > TextEdit, etc.) which use the standard font dialog. I'm not sure about SubEthaEdit, but maybe they are Cocoa apps. > I saw no difference between FMCreateFontFamilyIterator() and > ATSFontFamilyIteratorCreate(). That means the change to ATS does not help. Though it is possible to add some ad-hoc workaround, I'm rather negative about that because Apple might revert the behaviour of the Font Manager/ATS in subsequent updates of Tiger, and text drawing (and font enumeration, I think) in Carbon Emacs will be changed to use ATSUI in version 23. YAMAMOTO Mitsuharu [EMAIL PROTECTED] _______________________________________________ Emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
