Re: char-displayable-p issue

[Kenichi Handa <handa@m17n.org>]

In article <20031021232240.14826.qmail@web60306.mail.yahoo.com>, Michael Mauger <mmaug@yahoo.com> writes:

> [1  <multipart/alternative (7bit)>]
> [1.1  <text/plain; us-ascii (7bit)>]
> I can't reproduce that bug. When I turned on ruler-mode, I
> see both characters in the ruler head. Isn't it a bug
> specific to Windows?

> Yes, it seems the problem is specific to Windows. Work
> well on my GNU/Linux box.

> I'm not sure that this is just a Windows issue -- it may
> affect some X implementations as well.  The problem seems
> to be that the wildcard pattern generated in
> `char-displayable-p' is not matching multiple hyphen
> separated portions of the font name.  That is,
> '-*-*-iso8859-1' doesn't match any fonts while
> '-*-*-*-*-*-*-*-*-*-*-*-*-iso8859-1' does.

> Here's a patch that corrects the problem (and should work
> reliably on all X implementations) but which runs very
> slowly on Windows.

Ummm, I didn't know that such a server exists.  How about
'-*-iso8859-1'?  Doest it match all iso8859-1 fonts?  If so,
instead of just changing "-*-" to "-*-*-*-*-*-*-*-*-*-*-*-",
generating the most compact font-pattern (i.e. no succeeding
wildcards) will solve the problem without making Windows
version slow.

Could you try that?

Even if that doesn't work, your patch is not enough.  I
think we must change the length of "-*-..-*-" according to
the form of car of font-pattern ("FOUNDRY-FAMILY",
"*FAMILY", or "FOUNDRY*")

---
Ken'ichi HANDA
handa@m17n.org