[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#920336: Xterm doesn't support double-sized characters (DECDHL) when using Xft (client-side) fonts



On Thu, Jan 24, 2019 at 02:06:02PM +0300, Andrey ``Bass'' Shcheglov wrote:
> Hello Thomas,
> 
> Whenever I configure xterm to use core X11 fonts:
> 
> > *.vt100.renderFont:             False
> > *.vt100.locale:                 False
> > *.vt100.font:                   -monotype-courier
> > new-medium-r-normal--*-120-*-*-m-*-koi8-r
> 
> it renders double-sized characters (DECDHL) properly.
> 
> But when I configure it to use client-side fonts:
> 
> > *.vt100.renderFont:             True
> > *.vt100.faceName:               Courier New:antialias=false
> > *.vt100.faceSize:               12
> > *.vt100.utf8:                   1
> > *.vt100.utf8Fonts:              True
> > *.vt100.utf8Title:              True
> 
> it fails to render double-sized characters, which can be confirmed via
> the vttest utility.

xterm patch #349 implements this feature:

	reorganize text-drawing to make it possible to investigate using Xft to
	implement VT100-style double-sized characters.  While doing this, made
	a workaround for apparent Xft bug which loses its drawable state when
	switching from 132 to 80 columns.

(the workaround refers to the double-buffer feature, which is not completely
resolved yet, but unrelated to this report).

-- 
Thomas E. Dickey <dickey@invisible-island.net>
https://invisible-island.net
ftp://ftp.invisible-island.net

Attachment: signature.asc
Description: PGP signature


Reply to: