public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "julesbertholet at quoi dot xyz" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug localedata/31370] New: wcwidth() does not treat DEFAULT_IGNORABLE_CODE_POINTs as zero-width
Date: Sun, 11 Feb 2024 16:41:12 +0000 [thread overview]
Message-ID: <bug-31370-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=31370
Bug ID: 31370
Summary: wcwidth() does not treat DEFAULT_IGNORABLE_CODE_POINTs
as zero-width
Product: glibc
Version: 2.40
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: localedata
Assignee: unassigned at sourceware dot org
Reporter: julesbertholet at quoi dot xyz
CC: libc-locales at sourceware dot org
Target Milestone: ---
Unicode specifies (https://www.unicode.org/faq/unsup_char.html#3) that
characters with the `Default_Ignorable_Code_Point` property
> should be rendered as completely invisible (and non advancing, i.e. “zero width”), if not explicitly supported in rendering.
Hence, `wcwidth()` should give them all a width of 0, with two exceptions:
- the soft hyphen (U+00AD SOFT HYPHEN) is assigned width 1 by longstanding
precedent
- U+115F HANGUL CHOSEONG FILLER combines with jungseong and jongseong jamo to
form a width-2 syllable block, and should therefore keep its width 2
However, `wcwidth()` currently also incorrectly assigns non-zero width to
U+3164 HANGUL FILLER and U+FFA0 HALFWIDTH HANGUL FILLER.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2024-02-11 16:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 16:41 julesbertholet at quoi dot xyz [this message]
2024-02-11 16:55 ` [Bug localedata/31370] " julesbertholet at quoi dot xyz
2024-02-12 13:45 ` carlos at redhat dot com
2024-02-13 22:53 ` maiku.fabian at gmail dot com
2024-02-14 18:02 ` julesbertholet at quoi dot xyz
2024-02-14 18:27 ` carlos at redhat dot com
2024-02-14 20:47 ` julesbertholet at quoi dot xyz
2024-02-14 20:49 ` julesbertholet at quoi dot xyz
2024-02-16 17:43 ` carlos at redhat dot com
2024-02-18 18:20 ` julesbertholet at quoi dot xyz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-31370-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).