Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#27500 - [xterm] truncated fonts

Attached to Project: Arch Linux
Opened by orbisvicis (orbisvicis) - Friday, 09 December 2011, 06:55 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 20 May 2012, 08:16 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Can we make it a priority to upgrade to xterm 276

Patch 276 fixes what I find to be an annoying bug: underscores are indistinguishable from spaces
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Sunday, 20 May 2012, 08:16 GMT
Reason for closing:  Fixed
Additional comments about closing:  Should be fixed with latest upstream updates.
Comment by orbisvicis (orbisvicis) - Friday, 09 December 2011, 07:11 GMT
Nevermind, patch #276 is *supposed* to fix the FreeType changes, but after testing I realize it does not in all (esp. mine) cases. I have sent an email to the xterm creator.
Comment by orbisvicis (orbisvicis) - Sunday, 11 December 2011, 09:03 GMT
  • Field changed: Percent Complete (100% → 0%)
Patch 276 is indeed needed, but it is not an automagic fix. Freetype 2.4.6 reduced the ascender/descender values (line spacing) to fix an incorrect metric, this results in some truncated fonts (DejaVu Sans Mono set to pixelsize=13.5) in xterm. The workaround is to change the scaleHeight resource setting (I found 1.05 to match pre FreeType 2.4.6 line spacing with DejaVu Sans Mono pointsize=10 and Xft DPI=100). XTerm patch 276 is needed to modify TrueType clipping limits in relation to the scaleHeight value, otherwise truncation still occurs.
Comment by Andreas Radke (AndyRTR) - Sunday, 13 May 2012, 08:02 GMT
Has this been fixed meanwhile?