From: Michael Mauger <mmaug@yahoo.com>
Cc: emacs-devel@gnu.org, Kenichi Handa <handa@m17n.org>
Subject: Re: char-displayable-p issue
Date: Tue, 28 Oct 2003 07:12:01 -0800 (PST) [thread overview]
Message-ID: <20031028151201.53330.qmail@web60304.mail.yahoo.com> (raw)
In-Reply-To: <uvfq9vklv.fsf@jasonrumney.net>
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 <mmaug@yahoo.com>
* 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 <jasonr@gnu.org> wrote:
> Michael Mauger <mmaug@yahoo.com> 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
next prev parent reply other threads:[~2003-10-28 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 23:48 char-displayable-p issue Michael Mauger
2003-10-28 8:21 ` Jason Rumney
2003-10-28 15:12 ` Michael Mauger [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 19:09 Michael Mauger
2003-10-22 19:53 ` Jason Rumney
2003-10-23 20:21 ` Michael Mauger
2003-10-21 23:22 Michael Mauger
2003-10-22 5:51 ` Kenichi Handa
2003-10-22 16:00 ` Michael Mauger
2003-10-08 7:04 David PONCE
2003-10-13 23:40 ` Kenichi Handa
2003-10-14 5:56 ` David Ponce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031028151201.53330.qmail@web60304.mail.yahoo.com \
--to=mmaug@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=handa@m17n.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).