unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David De La Harpe Golden <david@harpegolden.net>
To: Stephen Berman <Stephen.Berman@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: (re)display problems after font backend merge
Date: Fri, 23 May 2008 05:16:11 +0100	[thread overview]
Message-ID: <4836450B.7000403@harpegolden.net> (raw)
In-Reply-To: <87lk226ppg.fsf@escher.local.home>

Stephen Berman wrote:
> 
> The (active) mode line face now displays Helvetica correctly.  Note,
> however, that in the inactive mode line face the characters are wider,

And not anti-aliased?  Was this still with FontBackend: xft ?

And [welcome to complication, Level 2] did you have fontconfig/xft set
to allow bitmap fonts or not?  While most linux distros now default to
"no", if fontconfig/xft /is/ using bitmap fonts, then "new" font
handling can still, depending of course on the font, result in
x-core-font-like-in-appearance rendering, you see! (including in emacs
with FontBackend: xft, as far as I can tell. Hmmm.)

At least if you're on debian  or a debian-oid (e.g. ubuntu...), this is
usually controlled by which one of
/etc/fonts/conf.avail/70-yes-bitmaps.conf or
/etc/fonts/conf.avail/70-no-bitmaps.conf
is symlinked in to /etc/fonts/conf.d/
(if you change this, you may have to run fc-cache -fv )

I recommend "no".  Unless you really have a need of particular glyphs
from or just can't live without some old favorite (probably monospace)
bitmap font I guess.

If you do enable bitmaps in fontconfig, try
"fc-list :scalable=False family" in a shell to get the fontconfig names
for bitmap fonts usable in fontconfig/xft apps...














  reply	other threads:[~2008-05-23  4:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-15 18:45 (re)display problems after font backend merge Stephen Berman
2008-05-16  0:57 ` Kenichi Handa
2008-05-16 10:22   ` Stephen Berman
2008-05-17  3:19     ` David De La Harpe Golden
2008-05-17 12:30       ` Stephen Berman
2008-05-17 14:02         ` David De La Harpe Golden
2008-05-17 18:37           ` Stephen Berman
2008-05-18  3:30             ` David De La Harpe Golden
2008-05-18 18:19               ` Stephen Berman
2008-05-22 20:36                 ` Stephen Berman
2008-05-23  4:16                   ` David De La Harpe Golden [this message]
2008-05-23 12:28                     ` Stephen Berman
2008-05-23 16:10                       ` David De La Harpe Golden
2008-05-23 17:03                         ` Stephen Berman
2008-05-23 17:37                           ` David De La Harpe Golden
2008-05-23 19:42                             ` James Cloos
2008-05-23 20:41                             ` Stephen Berman
2008-05-23 21:57                               ` David De La Harpe Golden
2008-05-24  1:16                                 ` James Cloos
2008-05-24 23:01                                 ` Stephen Berman
2008-05-27 13:17                   ` Stephen Berman

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=4836450B.7000403@harpegolden.net \
    --to=david@harpegolden.net \
    --cc=Stephen.Berman@gmx.net \
    --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).