unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Mauger <mmaug@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: char-displayable-p issue
Date: Wed, 22 Oct 2003 09:00:43 -0700 (PDT)	[thread overview]
Message-ID: <20031022160043.68916.qmail@web60304.mail.yahoo.com> (raw)
In-Reply-To: <200310220551.OAA07920@etlken.m17n.org>

--- Kenichi Handa <handa@m17n.org> wrote:
> In article <20031021232240.14826.qmail@web60306.mail.yahoo.com>,
> Michael Mauger <mmaug@yahoo.com> writes:
> 
> > 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*")

I tried '-*-iso8859-1' and it also failed.  The problem appears to be in
the Windows implementation of x-list-fonts (w32_list_fonts in
src/w32fns.c).  The wildcarding is obviously not working as intended.

(length (x-list-fonts "-*-*-*-*-*-*-*-*-*-*-*-*-iso8859-1")) 
= 584
(length (x-list-fonts "-*-iso8859-1"))
= 0

I'll take a look at w32_list_fonts but I am very rusty on Windows
internals.  

-- Michael

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

  reply	other threads:[~2003-10-22 16:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-21 23:22 char-displayable-p issue Michael Mauger
2003-10-22  5:51 ` Kenichi Handa
2003-10-22 16:00   ` Michael Mauger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-27 23:48 Michael Mauger
2003-10-28  8:21 ` Jason Rumney
2003-10-28 15:12   ` Michael Mauger
2003-10-22 19:09 Michael Mauger
2003-10-22 19:53 ` Jason Rumney
2003-10-23 20:21   ` 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=20031022160043.68916.qmail@web60304.mail.yahoo.com \
    --to=mmaug@yahoo.com \
    --cc=emacs-devel@gnu.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).