Re: [Aquamacs-bugs] Re: incorrect fontification of non-ascii chars on Mac OS X 10.4

[David Reitter]

On 30 Jun 2005, at 04:34, YAMAMOTO Mitsuharu wrote:
>   (create-fontset-from-mac-roman-font
>    "-*-FAMILY-medium-r-normal--SIZE-*-*-*-*-*-mac-roman" nil "NAME")
>
> would do the right thing for normal use.  If one also want to use ETL
> fonts, one can refer to how "fontset-mac" is defined.

OK.

I'm doing this now, and the definition of a couple of fontsets in  
different sizes (around 25 fontsets) takes over three seconds. Since  
we define the fontsets at startup time, this  represents an issue for  
us.

Can fontset creation handled on demand some how?

Why do we handle fonts lust like on X11 again in the Carbon port?
Do dozens of packages depend on specific fonts being set via the X11  
font-specs?
Does it enable people to actually exchange / share font-settings  
between the Carbon port and the X11 port?

I hope the font handling can and will be revised when the unicode  
branch is merged.