Re: fail on osx between 2/4/2009 and 2/5/2009

[Kenichi Handa <handa@m17n.org>]

In article <49917BE9.6020903@gnu.org>, Jason Rumney <jasonr@gnu.org> writes:

> Kenichi Handa wrote:
> > Ah!  Now I see why the current code doesn't work in
> > Cocoa/GNUstep port.  Hmmm, I'll think about the solution.  I
> > want to treat `mathematical-bold', etc. as a a kind of
> > script-subgroup, not a script.
> >   

> That would be better for Windows too. Previously there was a convenient 
> correspondence between the scripts in fontset.el and opentype unicode 
> subranges. Introducing finer granularity in fontset.el makes the job of 
> finding a matching font much harder.

I'm now thinking about these changes:

(1) Revert script-representative-chars to the previous
    state; i.e. single entry for mathematical.

(2) Add :chars property to font-spec.  The value is a list
    or a vector of characters; the same as that of
    script-representative-chars.  This value supersedes what
    defined in script-representative-chars.

(3) In the default fontset, for each subgroup of
    mathematical characters, register a font-spec with
    :script as 'mathematical and :chars as proper values for
    the subgroup.

(4) Modify ftfont_list to pay attention to :chars property.
    Though, I don't know if the other backends can utilize
    it.

---
Kenichi Handa
handa@m17n.org