public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug localedata/24658] wcwidth inconsistencies with Unicode 12.1 Date: Tue, 21 May 2024 19:00:39 +0000 [thread overview] Message-ID: <bug-24658-131-xELeCKbaAx@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-24658-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=24658 Mike FABIAN <maiku.fabian at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maiku.fabian at gmail dot com, | |tg at mirbsd dot de --- Comment #2 from Mike FABIAN <maiku.fabian at gmail dot com> --- Do you have any examples where the current way of treating these as width 2 causes problems? I checked again with the fonts I have on my system and these are still quadratic in most fonts. The hexagrams U+4DC0 to U+4DFF are also seem to be quadratic in most fonts although I found some fonts like "DejaVu Sans" and "Everson Mono" where they are rectangular, although still wider even there then "single width" (wider than half a square). I am reluctant to change this unless there is a good reason why this needs to change as it was requested by Thorsten Glaser (added to CC:) in https://sourceware.org/bugzilla/show_bug.cgi?id=21750#c0 it seemed to make sense at the time and nobody complained about that for quite a while. So why should these change now? -- You are receiving this mail because: You are on the CC list for the bug.
next parent reply other threads:[~2024-05-21 19:00 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-24658-131@http.sourceware.org/bugzilla/> 2024-05-21 19:00 ` maiku.fabian at gmail dot com [this message] 2024-05-22 0:03 ` tg at mirbsd dot de 2024-05-22 9:18 ` maiku.fabian at gmail dot com
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-24658-131-xELeCKbaAx@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: linkBe 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).