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] wcwidth() does not treat DEFAULT_IGNORABLE_CODE_POINTs as zero-width
Date: Wed, 14 Feb 2024 20:47:52 +0000 [thread overview]
Message-ID: <bug-31370-131-PTTfTpZmyB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31370-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31370
--- Comment #5 from Jules Bertholet <julesbertholet at quoi dot xyz> ---
> What do the libicu APIs return for these characters?
They don't. Unicode does not in general have a concept of how many "cells" a
character should take up in a terminal or with a fixed-width font. Some
characters are specified to be 0-width/non-advancing, and there is also a
limited concept of "East Asian Wide" defined by UTR 11
<https://www.unicode.org/reports/tr11/>. But the displayed width of many
characters depends on the context, surrounding characters, the particular font,
etc. `wcwidth()See <https://www.unicode.org/L2/L2023/23107-terminal-suppt.pdf>
for some more background.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-02-14 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 16:41 [Bug localedata/31370] New: " julesbertholet at quoi dot xyz
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 [this message]
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-PTTfTpZmyB@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).