On Sat, May 15, 2021 at 04:11:12PM +0200, Uwe Waldmann wrote: > Package: xterm > Version: 344-1+deb10u1 > Severity: important > > Dear Maintainer, > > xterm renders all characters between U+A7BA and U+A7F6 with width zero, > that is, not at all, even if they are present in the chosen font. > For instance,
According to https://unicodeplus.com/U+A7BA The character Ꞻ (Latin Capital Letter Glottal A) is represented by the Unicode codepoint U+A7BA. It is encoded in the Latin Extended-D block, which belongs to the Basic Multilingual Plane. It was added to Unicode in version 12.0 (March, 2019). It is HTML encoded as Ꞻ. xterm #344 is a little earlier than that. Its fallback copy of wcwidth doesn't list that range (I updated the table to Unicode 12 in #345, and added a test-driver around that time). The system wcwidth doesn't cover that range either. Characters which aren't known to wcwidth are treated as nonprinting... > printf '<\uA7B9>\n' > > displays "<u>" with a slash through "u" (correct), whereas > > printf '<\uA7BA>\n' > > displays "<>" (incorrect) instead of "<A>" with an apostrophe before > "A". The problem shows up with arbitrary fonts (both pcf and otb are > affected). Using -mk_width does not change the situation. > > (In Debian 9.1, it still worked correctly.) hmm - which version of xterm was that? I'm guessing that it was #327 (it should not have worked, but there's always the possibility that I fixed a bug which was making it appear to work) -- Thomas E. Dickey <dic...@invisible-island.net> https://invisible-island.net ftp://ftp.invisible-island.net
signature.asc
Description: PGP signature
