emacs-pretest-bug
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Carbon Emacs uses incorrect bold and italics fonts


From: Orca
Subject: Re: Carbon Emacs uses incorrect bold and italics fonts
Date: Wed, 21 Sep 2005 09:11:46 -0700 (PDT)

--- YAMAMOTO Mitsuharu <address@hidden> wrote:

> >>>>> On Fri, 16 Sep 2005 12:27:48 -0700 (PDT), Orca <address@hidden>
> said:
> 
> > Carbon Emacs does not properly load styles for some fonts. The key
> > font with which I am having trouble is Bitstream Vera Sans Mono. The
> > free font has specific typefaces for bold and italics styles. Carbon
> > Emacs does not load these extra faces properly. Applying a bold
> > style to Bitstream Vera Sans Mono should use Bitstream Vera Sans
> > Mono Bold within the same font family. Instead, Carbon Emacs
> > utilizes fonts in a way that the Font Manager incorrectly creates
> > its own bold and italics glypths. I suspect this has something to do
> > with the way that font names and styles are mapped into requesting
> > fonts from the FontManager, but I'm not familiar enough with Carbon
> > font programming to know exactly what's going wrong.
> 
> The Font Manager regards "Bitstream Vera Sans Mono", "Bitstream Vera
> Sans Mono Bold", "Bitstream Vera Sans Mono Oblique", and "Bitstream
> Vera Sans Mono Bold Oblique" as different font families just like
> "Courier" and "Times" are different.
> 
> Possibily ATS regards them as a single font family, but I've never
> tried that.  If so, future versions of Emacs might handle such a
> situation.

I originally noticed then after reinstalling my system, subsequently
upgrading from Panther to Tiger. 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>

This issue does not show up in other text editors (SubEthaEdit, TextEdit,
etc.) which use the standard font dialog. Perhaps it's something specific
to the use of enumerating fonts and font families? In a simple test, I saw
no difference between FMCreateFontFamilyIterator() and
ATSFontFamilyIteratorCreate().

-Chris

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]