This is the mail archive of the libc-locales@sourceware.org mailing list for the GNU libc locales project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug localedata/22074] charmaps/UTF-8: wcwidth for U+1160-U+11FF (Hangul Jungseong and Jongseong) should be 0


https://sourceware.org/bugzilla/show_bug.cgi?id=22074

--- Comment #4 from Mike Frysinger <vapier at gentoo dot org> ---
(In reply to Mike FABIAN from comment #1)
> But we cannot really do anything about the context, so we have to decide
> for one width to use.

today that is true.  long term, i think we'll need to figure out something
better similar to UAX29.  it wouldn't help with wcwidth, but it would for
wcswidth.
  http://www.unicode.org/reports/tr29/

so i think for today, supporting the common case and not the degenerate/invalid
cases makes sense.  which is to say, marking them as wcwidth of 0.

(In reply to Troy Korjuslommi from comment #2)
> Aren't Korean chars usually full width? I.e. wcwidth 2.

the precomposed hangul forms are wcwidth of 2:
  https://en.wikipedia.org/wiki/Hangul_Syllables

so i guess not only would we want to change the two sets to 0, we'd want to
change the first set to 2.  that way we'd line up with the precomposed forms
better.

i think that should get us closer, but it'd still be an approximation.  maybe
we should just focus on wcswidth here ?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]