Subject: Re: [9front] [PATCH] introduce code points above BMP to /lib/unicode
Date: Mon, 17 Oct 2022 08:34:06 +0200 [thread overview]
Message-ID: <5B9E186DD7F2C4E2910241F9FDEB0C09@wopr.sciops.net> (raw)
On Mon Oct 17 07:25:49 +0200 2022, email@example.com wrote:
> Our /lib/unicode is a bit out of date, this updates our stripped down
> version of UnicodeData.txt that we keep in /lib to cover characters
> and code ranges above the Basic Multilingual Plane.
> This does balloon the file a bit compared to the ~200k original.
> ; 800k /lib/unicode
> The full patch is attached. Of note the non-zero padding of the BMP
> range is replicated in the upstream UnicodeData.txt, I would be open
> to zero padding ours but this would change the results of existing
> scripts that use look(1) with /lib/unicode.
> Not sure how much use others get out of /lib/unicode, but wanted
> to ask if people thought it was worth the size to update.
I'm definitely in favor, thanks for doing this. Maybe a problem on my
end, but I can't gunzip the attached patch.
next prev parent reply other threads:[~2022-10-17 6:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 5:24 Jacob Moody
2022-10-17 6:34 ` qwx [this message]
2022-10-17 20:28 ` Jacob Moody
2022-10-23 5:07 ` qwx
2022-10-23 14:28 ` ori
2022-10-23 16:58 ` qwx
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 NNTP newsgroup(s).