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: handa@m17n.org, emacs-devel@gnu.org
Subject: Re: (re)display problems after font backend merge
Date: Sat, 17 May 2008 04:19:12 +0100	[thread overview]
Message-ID: <482E4EB0.3070003@harpegolden.net> (raw)
In-Reply-To: <87fxsiczun.fsf@escher.local.home>

Stephen Berman wrote:

> For ascii:
> 
> -unknown-DejaVu Sans Mono-normal-normal-normal-*-12-*-*-*-m-0-iso8859-1
>

Call it (a)

> For the non-ascii characters:
> 
> -gnu-unifont-medium-r-normal--16-160-75-75-p-80-iso10646-1
>

Call it (b)

This is mostly me trying to understand something:

Those (a) and (b) look like XLFD font specs, as used by X core 1-bit
fonts - see output of command xlsfonts [*]

> This is post-merge, in the pre-merge buffer, the corresponding line of
> the character description for both ascii and non-ascii characters is
> this:
> 
> dejavu sans mono:pixelsize=12:foundry=unknown:weight=medium:slant=r:width=normal
>

Call it (c).   That looks like a fontconfig font spec, as used by xft
antialiased fonts - see output of fc-list [*]

Are you setting X resource "Emacs.FontBackend: xft"? I've found that
without that, I get a strange mix of decent and horrible font rendering
as xft fonts (yay) and x core fonts (boo) are apparently both used somehow?

:::::: I've just found that, at least post font-backend merge and
possibly for some time before, emacs /even with/ FontBackend: xft
returns XLFD-style specs even when it's clearly using xft rendering and
fonts that I _know_ I didn't make available to X core font handling - I
find that kind of confusing, emacs must be just inventing and using
XLFDs internally ???
e.g. describe-char gives me, which looks like your (a), though I naively
expected something like (c):

-unknown-DejaVu Sans Mono-normal-normal-normal-*-14-*-*-*-m-0-iso10646-1

A sort of "synthetic XLFD" that emacs has invented.


::::: I would speculate that you [Stephen] don't have FontBackend: xft
and your (a)  is one of these synthetic XLFDs and (b) is a "real" XLFD
corresponding to an X core font ??

So some of your characters (those in (b)) are getting drawn with
X core font rendering and some with Xft font rendering (those in (a)),
leading to at least some of the visually ugly appearance that is a
"feature" of all X core font handling (e.g. lack of antialiasing, poor
alignment)  ???



[*] Sometimes the same font dirs are added to paths for both core fonts
and fontconfig, so the same fonts show up in both xlsfonts and fc-list,
but that's a bad assumption to make in general.










  reply	other threads:[~2008-05-17  3:19 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 [this message]
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
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=482E4EB0.3070003@harpegolden.net \
    --to=david@harpegolden.net \
    --cc=Stephen.Berman@gmx.net \
    --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).