This is the mail archive of the
libc-locales@sourceware.org
mailing list for the GNU libc locales project.
[Bug localedata/22073] charmaps/UTF-8: wcwidth of U+00AD (soft hyphen): 0 or 1 ?
- From: "maiku.fabian at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: libc-locales at sourceware dot org
- Date: Fri, 15 Sep 2017 08:23:56 +0000
- Subject: [Bug localedata/22073] charmaps/UTF-8: wcwidth of U+00AD (soft hyphen): 0 or 1 ?
- Auto-submitted: auto-generated
- References: <bug-22073-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22073
Mike FABIAN <maiku.fabian at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #25 from Mike FABIAN <maiku.fabian at gmail dot com> ---
(In reply to Mike FABIAN from comment #24)
> (In reply to Thorsten Glaser from comment #23)
> > > Nope. SHY-aware apps by definition never send SHY to the terminal, they either send a regu
> > > lar hyphen U+2D or nothing at all, that's what makes them SHY-aware. (Especially since in
> > > several fonts the glyph of SHY is empty, it looks like a space.) If an app ever sends a SH
> > > Y to the terminal emulator, it is SHY-unaware.
> > >
> > > Hence for SHY-aware apps, wcwidth() of SHY is irrelevant.
> >
> > OK, granted, if that is the sense, you are, of course, correct.
> > (But that also means that, if it’s irrelevant for them, which,
> > again, if they send U+002D to the terminal instead, it is, then
> > all the more reason to stick to 1.)
>
> Yes,that is really a good reason to stick to 1.
So it looks like we have reached some agreement that width 1 is OK
for the soft hypen and I can close this bug as FIXED, right?
Closing as FIXED.
--
You are receiving this mail because:
You are on the CC list for the bug.