@Ambrus, Marc
I ran urxvt and xterm with a clean .Xresources.
Locale is set to en_US.UTF-8.
xterm
Resources: default
Command: xterm +fbx -fa inconsolata:size=12
urxvt
Configure: --enable-everything --enable-256-color --enable-assert
--with-res-class=URxvt-debug
Resources: default
Command: urxvt -sbg -fn xft:inconsolata:size=12
Thanks to the ISO-14755 mode I found out that Inconsolata is missing the
box drawing glyphs (bleh), further confirmed by the lack of entries in
the character map. Of course urxvt was not behaving correctly, it was
fetching those glyphs from other random fonts.
> What urxvt option do you refer to?
skipBuiltinGlyphs. The corresponding xterm option, to the best of my
knowledge, should be forceBoxChars. I guess I should have worded better
my statement.
@Josip
Yes, the font is Inconsolata through Xft, 12pt.
Marco
On 12/29/2016 06:08 AM, Marc Lehmann wrote:
On Wed, Dec 28, 2016 at 11:20:41AM +0100, Marco Buzzanca <[email protected]>
wrote:
I've noticed that urxvt (6.22) renders box-drawing characters like │ or ┼
incorrectly compared to xterm.
urxvt only renders its own box drawing characters if the font you are using
doesn't provide them - so first you'd have to find out where the glyphs are
from (using iso-14755 mode for example).
if they are from the "built-in support font", then you might have a
problem with urxvt. otherwise, it's the font you are using and urxvt can't
do anything about it, and you'd need a better font.
Both urxvt (left) and xterm (right) have the respective options to force box
glyphs off.
What urxvt option do you refer to?
_______________________________________________
rxvt-unicode mailing list
[email protected]
http://lists.schmorp.de/mailman/listinfo/rxvt-unicode
