On Thu 09 Jul 2020 at 18:29:15 +0200, Tadziu Hoffmann wrote: > Could it perhaps be related to your locale, in that CTWM > chooses the font in some particular encoding that has > different metrics? What happens if you start CTWM > explicitly using the "C" locale, as in > > LANG=C LANGUAGE=C LC_ALL=C ctwm & > > (and whatever else needs to be (un)set)? > Or maybe using Latin-1 (LC_CTYPE=en_US.ISO8859-1)?
I was about to suggest the same thing. I think I had some UTF-8 font related changes at some point in the past. Mainly because the UTF-8 fonts contain so many more characters, the maximum ascenders and descenders are a lot bigger than with more limited Latin-1 character sets. I think there was even some code change somewhere in ctwm to compensate for this, but I'm now trying very hard to remember where that was... (and currently `bzr qlog` has broken on my system... claiming it can't find a module named sip, even though I have sip for both python 2.7 and 3.7...) -Olaf. -- Olaf 'Rhialto' Seibert -- rhialto at falu dot nl ___ Anyone who is capable of getting themselves made President should on \X/ no account be allowed to do the job. --Douglas Adams, "THGTTG"
signature.asc
Description: PGP signature
