Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#961362: fonts-terminus-otb: In rxvt-unicode, M and m characters missing the left vertical stroke

79 views
Skip to first unread message

Ian Zimmerman

unread,
May 23, 2020, 11:50:03 AM5/23/20
to
Package: fonts-terminus-otb
Version: 4.48-2
Severity: important
Tags: upstream

The subject almost says it all. But the effect is only visible after whitespace, it seems.
The PCF format font (which I assume is generated from the same source) has no such problem.

Also, I tried to unpack the Arch Linux package of the same name and install the files
manually, and the same problem happens there, so this is not Debian specfic.

Specifically, I use the 12 size font. Display is Dell U2410, about 94 dpi.
fontconfig: 2.13.1-2
freetype: 2.9.1-3+deb10u1

-- System Information:
Debian Release: 10.4
APT prefers stable
APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages fonts-terminus-otb depends on:
ii xfonts-utils 1:7.7+6

fonts-terminus-otb recommends no packages.

Versions of packages fonts-terminus-otb suggests:
pn xfonts-terminus-oblique <none>
ii xserver-xorg [xserver] 1:7.7+19

Anton Zinoviev

unread,
May 25, 2020, 6:10:02 AM5/25/20
to
On Sat, May 23, 2020 at 08:42:59AM -0700, Ian Zimmerman wrote:
>
> The PCF format font (which I assume is generated from the same source)
> has no such problem.

I suppose this is not a font problem but a problem of the rendering
engine. The rendering engine of the OTB fonts is more sofisticated than
the rendering engine of the PCF fonts. It can render the fonts in
arbitrary font sizes (including non-integer sizes).

But as usually, with sofistication come problems, undebugged cases, etc.

> Specifically, I use the 12 size font.

How about 13 size? Or maybe something like 12.1, 12.2, 12.3 or 12.4
(or 12,1, 12,2, 12,3 and 12,4 in locales with decimal comma)?

Anton Zinoviev

Ian Zimmerman

unread,
May 28, 2020, 2:40:02 AM5/28/20
to
How do I actually select such a non-integral size?

Right now I configure it 3 ways:

- in .Xresources:

echo "URxvt.font: xft:${ITZ__MONO_FONT}" | xrdb -merge

- on the command line:

dzen2 -ta l -fn "$ITZ__MONO_FONT"

- via Elisp:

(setq default-frame-alist
`((menu-bar-lines . 0)
(font . ,(shell-command-to-string "fc-match -f '%{family}-%{size}'
\"${ITZ__MONO_FONT}\""))
(vertical-scroll-bars . nil)))

where ITZ__MONO_FONT="Terminus-12"

I don't think any of these contexts will allow a fractional size, or am I wrong?

Ian

Matti Hämäläinen

unread,
Jun 21, 2020, 6:00:04 PM6/21/20
to

Hello,

I ran into this problem myself (using "URxvt*font: xft:Terminus:pixelsize=20"
font spec), and seems it is some kind of bug in rxvt-unicode.
Xterm does not suffer from this issue with the same font spec.

The issue seems to reside in src/rxvtfont.C rxvt_font_xft::draw()
with the doublebuffered rendering, if you disable buffering via
"URxvt*buffered: false", the issue disappears at least for my use case.

But, disabling buffering is probably not a very efficient solution.

Also a kludge-patching line 1380 of src/rxvtfont.C:

- int x_ = buffered ? 0 : x;
+ int x_ = buffered ? 1 : x;

"fixes" the issue as well at least for the case I bothered to check, but
obviously that's not a good solution either.

Perhaps this issue should be transferred to package rxvt-unicode?

--
] ccr/TNSP ^ pWp :: c...@tnsp.org :: https://tnsp.org/~ccr/
] https://tnsp.org/hg/ -- https://www.openhub.net/accounts/ccr
] PGP key: 7BED 62DE 898D D1A4 FC4A F392 B705 E735 307B AAE3

Ian Zimmerman

unread,
Jul 26, 2020, 12:10:03 PM7/26/20
to
Package: fonts-terminus-otb
Followup-For: Bug #961362

FWIW, I have tried sizes 11 and 13 and they both have the problem.

Jimmy Sjölund

unread,
Aug 16, 2021, 11:30:03 AM8/16/21
to
I had no issues running Debian 10 but upgraded to Debian 11 this weekend and Terminus show the same issue in rxvt-unicode as described here.

0 new messages