public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: "maiku.fabian at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/26120] column width of  of some Korean JUNGSEONG/JONGSEONG characters wrong (should be 0)
Date: Sun, 21 Jun 2020 09:07:02 +0000	[thread overview]
Message-ID: <bug-26120-716-ut9GPFmB3g@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26120-716@http.sourceware.org/bugzilla/>

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

--- Comment #9 from Mike FABIAN <maiku.fabian at gmail dot com> ---
(In reply to Thorsten Glaser from comment #7)
> Erk… glibc is particular about not defining widths of not-defined characters.
> 
> Besides D7FC‥D7FF (which gave me an error in the output from my own
> scripts), D7C7‥D7CA are not yet assigned and so probably need to be excluded
> in glibc.
> 
> Should they ever be defined, we’ll need to adjust here, so it’s probably
> better to iterate over the entire D7C0‥D7FF range and ony change widths for
> defined codepoints from the current UCD version.

Thank you for noticing that!

I was aware that glibc has a problem with defining width of unassigned
characters, therefore I used 

 for key in list(range(0xD7B0, 0xD7FC)):

instead of 

 for key in list(range(0xD7B0, 0xD800)):

because D7FC and D7FF are undefined and localedef gave me errors
when I included them. Surprisingly localedef did not give  errors for the
unassigned D7C7‥D7CA ...

I had checked the range manually and thought all characters
from D7B0 to D7FB were assigned, but apparently I missed D7C7‥D7CA.

I improved the generator script a bit to omit the unassigned characters,
if these get defined in future, the script would add them.

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

  parent reply	other threads:[~2020-06-21  9:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16  5:43 [Bug localedata/26120] New: " maiku.fabian at gmail dot com
2020-06-16  5:44 ` [Bug localedata/26120] " maiku.fabian at gmail dot com
2020-06-16  5:45 ` maiku.fabian at gmail dot com
2020-06-16  5:46 ` maiku.fabian at gmail dot com
2020-06-16  5:47 ` maiku.fabian at gmail dot com
2020-06-16  5:47 ` maiku.fabian at gmail dot com
2020-06-16  5:58 ` maiku.fabian at gmail dot com
2020-06-16  8:26 ` maiku.fabian at gmail dot com
2020-06-16 11:53 ` fweimer at redhat dot com
2020-06-16 17:32 ` maiku.fabian at gmail dot com
2020-06-16 17:35 ` fweimer at redhat dot com
2020-06-20 21:19 ` tg at mirbsd dot de
2020-06-21  9:00 ` maiku.fabian at gmail dot com
2020-06-21  9:07 ` maiku.fabian at gmail dot com [this message]
2020-06-21 14:20 ` tg at mirbsd dot de
2020-06-23  7:08 ` maiku.fabian at gmail dot com
2020-06-23  7:33 ` tg at mirbsd dot de
2020-06-23  8:50 ` maiku.fabian at gmail dot com
2020-06-23  9:03 ` maiku.fabian at gmail dot com
2020-06-25 13:05 ` maiku.fabian at gmail dot com
2020-06-26 12:26 ` maiku.fabian at gmail dot com
2020-06-26 12:27 ` maiku.fabian at gmail dot com
2020-06-28 12:50 ` maiku.fabian at gmail dot com
2021-12-30  0:35 ` bruno at clisp dot org

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-26120-716-ut9GPFmB3g@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=libc-locales@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).