Gnus development mailing list
 help / color / mirror / Atom feed
From: Kenichi Handa <handa@m17n.org>
To: Reiner Steib <Reiner.Steib@gmx.de>
Cc: tzz@lifelogs.com, ding@gnus.org, emacs-devel@gnu.org
Subject: Re: Gnus problem with nil font in face definition
Date: Fri, 29 Feb 2008 16:28:34 +0900	[thread overview]
Message-ID: <E1JUzfW-0002Ua-IE@etlken.m17n.org> (raw)
In-Reply-To: <v9wsoohlu1.fsf@marauder.physik.uni-ulm.de> (message from Reiner Steib on Thu, 28 Feb 2008 21:23:18 +0100)

In article <v9wsoohlu1.fsf@marauder.physik.uni-ulm.de>, Reiner Steib <reinersteib+gmane@imap.cc> writes:

> On Thu, Feb 28 2008, Ted Zlatanov wrote:
> > It seems that the cause is faces that have the font set to nil, instead
> > of unspecified.  I don't know if this is a Gnus-only problem, and it may
> > be caused by an Emacs problem, so I am cc-ing both emacs-devel and ding.

> I'm quite sure that nothing in Gnus/Message has changed in this area,
> so it is probably related to the unicode merge (new font back end?)

> For those not using Gnus, a test case might be:

> - emacs -Q -fn '-misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1'

I found what is wrong with the current font-backend code.

% xlsfonts -fn -misc-fixed-*-*-*--20-200-75-75-c-100-iso10646-1

lists these fonts.

-misc-fixed-bold-r-normal--20-200-75-75-c-100-iso10646-1
-misc-fixed-bold-r-normal--20-200-75-75-c-100-iso10646-1
-misc-fixed-bold-r-semicondensed--20-200-75-75-c-100-iso10646-1
-misc-fixed-medium-o-normal--20-200-75-75-c-100-iso10646-1
-misc-fixed-medium-o-semicondensed--20-200-75-75-c-100-iso10646-1
-misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1
-misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1
-misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1
-misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1
-misc-fixed-medium-r-semicondensed--20-200-75-75-c-100-iso10646-1

but the result of

% xlsfonts -fn -misc-fixed-*-*-*--*-*-*-*-c-*-iso10646-1

doesn't contain this font:
-misc-fixed-bold-r-normal--20-200-75-75-c-100-iso10646-1

I'm now working on handling such a case correctly.
By the way, if you specify this font (i.e. a font whose bold
versoin also exists without auto-scaling):

-misc-fixed-medium-r-normal--18-120-100-100-c-90-iso10646-1

Emacs can find the correct bold version (at least in my
environment).

---
Kenichi Handa
handa@ni.aist.go.jp




  parent reply	other threads:[~2008-02-29  7:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m2wsos6joe.fsf@kenny.sha-bang.de>
2008-02-26 19:33 ` Default mm-uu-extract face hard to read on ttys Reiner Steib
2008-02-27 11:50   ` Sascha Wilde
2008-02-27 13:07     ` Bastien
2008-02-27 13:54       ` Sascha Wilde
2008-02-27 14:05         ` Bastien
2008-02-27 22:25     ` Reiner Steib
2008-02-28  8:53       ` Sascha Wilde
2008-02-28 17:07   ` Gnus problem with nil font in face definition (was: Default mm-uu-extract face hard to read on ttys) Ted Zlatanov
2008-02-28 17:51     ` Gnus problem with nil font in face definition Stefan Monnier
2008-02-28 19:04       ` Ted Zlatanov
2008-02-28 20:23     ` Reiner Steib
2008-02-28 21:53       ` Ted Zlatanov
2008-02-29  7:28       ` Kenichi Handa [this message]
2008-02-29 15:38         ` Ted Zlatanov

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1JUzfW-0002Ua-IE@etlken.m17n.org \
    --to=handa@m17n.org \
    --cc=Reiner.Steib@gmx.de \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=tzz@lifelogs.com \
    /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.
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 NNTP newsgroup(s).