9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Jacob Moody <moody@mail.posixcafe.org>
To: 9front@9front.org
Subject: [9front] [PATCH] introduce code points above BMP to /lib/unicode
Date: Sun, 16 Oct 2022 23:24:58 -0600	[thread overview]
Message-ID: <5e9c64f4-bad0-ce74-7e15-e8883598fcc2@posixcafe.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 664 bytes --]

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.


[-- Attachment #2.1: Type: text/plain, Size: 348 bytes --]

from postmaster@9front:
The following attachment had content that we can't
prove to be harmless.  To avoid possible automatic
execution, we changed the content headers.
The original header was:

	Content-Type: application/gzip; name="unicode.patch.gz"
	Content-Disposition: attachment; filename="unicode.patch.gz"
	Content-Transfer-Encoding: base64

[-- Attachment #2.2: unicode.patch.gz.suspect --]
[-- Type: application/octet-stream, Size: 117597 bytes --]

             reply	other threads:[~2022-10-17  5:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17  5:24 Jacob Moody [this message]
2022-10-17  6:34 ` qwx
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

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5e9c64f4-bad0-ce74-7e15-e8883598fcc2@posixcafe.org \
    --to=moody@mail.posixcafe.org \
    --cc=9front@9front.org \


* 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).