Dmitry Bogatov wrote on 22/05/2019: > > [2019-05-19 23:49] Paride Legovini <p...@ninthfloor.org> >> I tried with xterm and sakura, the Cyrillic string renders exactly as >> in stterm, with the correct character width and spacing. > >> Let me know if there is anything else I can try. > > Okay. I prepared kvm virtual machine image, that you can download > from "people.debian.org/~kaction/stterm-bug.img.xz". > > After it boots, it shows Xdm prompt. Log is as "user:useruser". You will > have default "dwm" instance. Press Alt-Shift-Enter and some terminal > will appear. > > There is ~user/I-Will-Show-You.sh script, that starts stterm to show > difference between cyrillic "Привет, мир!" and ascii "Hello, world!". > > Hope, you will see same thing as me. After that, you can get root > permission with su and "root:rootroot".
Hi, Using the VM I can reproduce the issue (well, obviously). My impression is that stterm is *not* using Terminus to render the Cyrillic letters, even if Terminus do have the needed glyphs. This is very clear when comparing stterm and urxvt (from rxvt-unicode): stterm -f Terminus-24 -e tail -f ~/test.txt urxvt -fn Terminus-24 -e tail -f ~/test.txt Forget the size and overlap problem and look at the Cyrillic "M" letter: the "wedge" of the letter is way deeper in stterm. The Cyrillic letters in stterm are from different, fallback font. The same font is used when a nonexisting font is specified, e.g. stterm -f NonExisting -e tail -f ~/test.txt and this reinforces the idea of a fallback mechanism being in place. This also somehow explains why I can't reproduce the problem locally: a different fallback font is probably used on my system as I have a different set of font packages installed. However I do see a difference between stterm and urxvt, and stterm is clearly using the wrong font for Cyrillic even on my system, while urxvt uses the correct font (Terminus is quite recognizable). I tried to reproduce by compiling st directly from the upstream source tree and I am able to reproduce the issue (as expected, as there are currently no patches in the Debian package). My conclusions are: - This is an actual bug in st, not a configuration issue; - The comparison with urxvt makes it apparent; - The bug belongs to upstream. Do you think you can follow-up to d...@suckless.org? Paride