all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: handa.kenichi@aist.go.jp (K.Handa)
Cc: xsrvmy@gmail.com, 35079@debbugs.gnu.org
Subject: bug#35079: 26.1; Font rendering - problem with bdf fonts
Date: Fri, 03 May 2019 11:36:14 +0300	[thread overview]
Message-ID: <837eb8nddt.fsf@gnu.org> (raw)
In-Reply-To: <87h8b2chv8.fsf@aist.go.jp> (handa.kenichi@aist.go.jp)

> From: handa.kenichi@aist.go.jp (K.Handa)
> Cc: xsrvmy@gmail.com, 35079@debbugs.gnu.org, handa@gnu.org
> Date: Sat, 13 Apr 2019 19:35:55 +0900
> 
> For this, I found that fontconfig gives 'spacing' parameter of that font
> as FC_CHARCELL.  I think the spacing of that font should be FC_DUAL.
> Anyway, src/xftfont.c of Emacs does not know about FC_CHARCELL.  So,
> emacs treats that font as a mono-space font.
> 
> I think you can modify the spacing paramter of that font to FC_DUAL by
> writing some code in ~/.fonts.conf.
> 
> Or, please try to apply this patch to src/xftfont.c, and rebuild emacs.

Should I install this change now?  Can it do any harm?

> I don't know the exact meaning of FC_CHARCELL.  I could't find it on the
> Internet.  Does anyone know what it means and why fontconfig uses it for
> the gnu unifont?

I found this in
https://github.com/freedesktop/xorg-libXft/blob/master/NEWS:

  Version 2.1.7

  Change FC_CHARCELL and FC_MONO interpretation.  FC_MONO no longer clips
  glyphs to charcell, you must specify FC_CHARCELL for that.

But I guess you saw this too?  It sounds like FC_CHARCELL is the same
as monospaced, but with clipping to character cell, whatever that may
mean.

Thanks.





  reply	other threads:[~2019-05-03  8:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02  5:31 bug#35079: 26.1; Font rendering - problem with bdf fonts Max Xiong
2019-04-02 14:56 ` Eli Zaretskii
2019-04-13 10:35   ` K.Handa
2019-05-03  8:36     ` Eli Zaretskii [this message]
2019-05-06 13:12       ` handa
2019-11-17  9:01     ` Lars Ingebrigtsen
2019-11-17 16:03       ` Eli Zaretskii
2019-11-17 16:32         ` Lars Ingebrigtsen

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=837eb8nddt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35079@debbugs.gnu.org \
    --cc=handa.kenichi@aist.go.jp \
    --cc=xsrvmy@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.