From: Eli Zaretskii <eliz@gnu.org>
To: Max Xiong <xsrvmy@gmail.com>, Kenichi Handa <handa@gnu.org>
Cc: 35079@debbugs.gnu.org
Subject: bug#35079: 26.1; Font rendering - problem with bdf fonts
Date: Tue, 02 Apr 2019 17:56:12 +0300 [thread overview]
Message-ID: <83sgv0foc3.fsf@gnu.org> (raw)
In-Reply-To: <CAAKArVHNwCtVP_kPzCc74AhTwRG89DqiSj5=p0C43ff8JGfOYw@mail.gmail.com> (message from Max Xiong on Tue, 2 Apr 2019 01:31:09 -0400)
> From: Max Xiong <xsrvmy@gmail.com>
> Date: Tue, 2 Apr 2019 01:31:09 -0400
>
> When loading a bdf or a pcf font, specifically unifont in my case, the width of characters is incorrect.
Does this happen only with Unifont, or with any BDF font?
> To reproduce:
> Download the bdf.gz file from the unifont website at http://unifoundry.com/unifont/index.html
> Change the extension to .bdf
> Install the font. In my case, I needed to copy it to ~/.local/share/fonts/misc/
> Run fc-cache -fv in the terminal.
> Start emacs.
> From the menu bar, choose options -> select default font.
> Search for and choose Unifont Sans Serif size 12 (size should go to 12 anyways).
>
> The unexpected result is that each character is rendered with a full width, as if there is a space after it. The
> cursor becomes square instead of a half-width rectangle.
This could be the realization of the danger described in the
commentary to ftfont.c:get_adstyle_property, or some other issue with
BDF fonts. I don't think they are used widely anymore, so maybe our
code accrued some bitrot.
> Additionally, note that this does NOT occur with the ttf version of unifont. Nor does this bug occur when I use
> the bdf unifont inside the gnome terminal.
CC'ing Handa-san, in the hope that he could look into this issue.
Thanks.
next prev parent reply other threads:[~2019-04-02 14:56 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 [this message]
2019-04-13 10:35 ` K.Handa
2019-05-03 8:36 ` Eli Zaretskii
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=83sgv0foc3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35079@debbugs.gnu.org \
--cc=handa@gnu.org \
--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.