[9front] [PATCH] introduce code points above BMP to /lib/unicode

[Jacob Moody <moody@mail.posixcafe.org>]

[-- 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.

Thanks,
moody

[-- 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 --]