Re: char-displayable-p issue

[Michael Mauger]

You can ignore the first patch -- the second one supercedes it.  I should
have clearer about that.

No rush -- I realize this is a significant change to a very complex and
critical piece of code.

Below is a correct version of the ChangeLog entry:

2003-10-27  Michael Mauger  <address@hidden>

        * w32fns.c (w32_normalize_xlfd): Added function.  Expands a
        partial XLFD specification into a fully qualified specification by
        filling in wildcards. Translates Windows-specific font format to a
        fully qualified XLFD specification.
        (w32_get_xlfd_field): Added function.  Returns a portion of a XLFD
        specification.
        (w32_to_x_font): Use "*" rather than "unknown" for unknown XLFD
        FOUNDRY.  Use "*" when FAMILY is empty.
        (x_to_w32_font): Rewritten.  Use `w32_normalize_xlfd' and
        `w32_get_xlfd_field' to parse XLFD string properly.
        (xlfd_strip_height): Rewrote to simplify and correct.
        (w32_font_match): Normalize XLFD pattern before stripping height
        or converting to a regex.  Because the pattern is fully qualified,
        wildcards now match "[^-]*" rather than ".*" as it did before.
        (w32_list_fonts): If face name has no wildcards then use it in
        Windows FontEnum to reduce the number of fonts enumerated.


--- Jason Rumney <address@hidden> wrote:
> Michael Mauger <address@hidden> writes:
> 
> > I've spent some time looking into the font enum code.  There were
> > several interrelated bugs involved in the matching of font
> > specifications.  I've attached a patch that addresses these
> > problems.  Here's the ChangeLog for these changes. 
> 
> Thank you. I'll take a look at both sets of changes over the next few
> days.
> 


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com