https://bugs.kde.org/show_bug.cgi?id=378124
Egmont Koblinger <egm...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egm...@gmail.com
--- Comment #1 from Egmont Koblinger <egm...@gmail.com> ---
gnome-terminal suffers from the same set of problems, see e.g.
https://bugzilla.gnome.org/show_bug.cgi?id=772812
https://bugzilla.gnome.org/show_bug.cgi?id=772890
Indeed plenty of codepoints changed from single-wide to double-wide as of
Unicode 9.0, and this causes tons of troubles (until all components of the
system update to 9.0).
glibc will receive Unicode 9.0 support in version 2.26 (it's already in git,
but missed 2.25). Based on what you say, Debian seems to forward-patch their
2.24.
> EastAsianWidth.txt of Unicode 8.0 didn't contain \u26a1
It may not contain this string in particular, it's inside an interval:
ftp://ftp.unicode.org/Public/8.0.0/ucd/EastAsianWidth.txt
26A0..26BD;N # So [30] WARNING SIGN..SOCCER BALL
ftp://ftp.unicode.org/Public/9.0.0/ucd/EastAsianWidth.txt
26A1;W # So HIGH VOLTAGE SIGN
> Wouldn't using the system's wcwidth (if available?) be preferable?
I guess so (see the second gnome-terminal link above).
--
You are receiving this mail because:
You are watching all bug changes.
