[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#988554: xterm does not render U+A7BA ... U+A7F6



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,

  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.)

Expected behavior:

Characters between U+A7BA and U+A7F6 should be rendered properly
if present in the given font(s), or replaced by a default character
otherwise.

-- System Information:
Debian Release: 10.9
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.104.1.pm64-smp (SMP w/4 CPU cores)
Kernel taint flags: TAINT_USER
Locale: LANG=en_US, LC_CTYPE=de_DE (charmap=ISO-8859-1), LANGUAGE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xterm depends on:
ii  libc6           2.28-10
ii  libfontconfig1  2.13.1-2
ii  libfreetype6    2.9.1-3+deb10u2
ii  libice6         2:1.0.9-2
ii  libtinfo6       6.1+20181013-2+deb10u2
ii  libutempter0    1.1.6-3
ii  libx11-6        2:1.6.7-1+deb10u1
ii  libxaw7         2:1.0.13-1+b2
ii  libxft2         2.3.2-2
ii  libxinerama1    2:1.1.4-2
ii  libxmu6         2:1.1.2-2+b3
ii  libxpm4         1:3.5.12-1
ii  libxt6          1:1.1.5-1+b3
ii  xbitmaps        1.1.1-2

Versions of packages xterm recommends:
ii  x11-utils  7.7+4

Versions of packages xterm suggests:
pn  xfonts-cyrillic  <none>

-- no debconf information


Reply to: