From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [NOOB ALERT] media player unicode symbols
Date: Thu, 22 Sep 2022 22:47:52 -0400 [thread overview]
Message-ID: <0A519E28E1E2009FE5F5C84F18C93390@eigenstate.org> (raw)
In-Reply-To: <82E06FF790ADA923E70B82E34A250BFC@ftrv.se>
Quoth Sigrid Solveig Haflínudóttir <sigrid@ftrv.se>:
> Patches welcome.
alright -- how does this one look?
diff 43a3a80be3cd9fe7e0f31efe5c24c3e321e07b08 uncommitted
--- a//lib/font/bit/vga/unicode.font
+++ b//lib/font/bit/vga/unicode.font
@@ -105,6 +105,70 @@
0xfe76 0xfefc vga.FE76-FEFC
0xfeff 0xfeff vga.FEFF-FEFF
0xfffd 0xfffd vga.FFFD-FFFD
+0x0000 0x07ff ../unifont/unifont.0000-07FF
+0x0800 0x0fff ../unifont/unifont.0800-0FFF
+0x1000 0x17ff ../unifont/unifont.1000-17FF
+0x1800 0x1fff ../unifont/unifont.1800-1FFF
+0x2000 0x27ff ../unifont/unifont.2000-27FF
+0x2800 0x2fff ../unifont/unifont.2800-2FFF
+0x3000 0x37ff ../unifont/unifont.3000-37FF
+0x3800 0x3fff ../unifont/unifont.3800-3FFF
+0x4000 0x47ff ../unifont/unifont.4000-47FF
+0x4800 0x4fff ../unifont/unifont.4800-4FFF
+0x5000 0x57ff ../unifont/unifont.5000-57FF
+0x5800 0x5fff ../unifont/unifont.5800-5FFF
+0x6000 0x67ff ../unifont/unifont.6000-67FF
+0x6800 0x6fff ../unifont/unifont.6800-6FFF
+0x7000 0x77ff ../unifont/unifont.7000-77FF
+0x7800 0x7fff ../unifont/unifont.7800-7FFF
+0x8000 0x87ff ../unifont/unifont.8000-87FF
+0x8800 0x8fff ../unifont/unifont.8800-8FFF
+0x9000 0x97ff ../unifont/unifont.9000-97FF
+0x9800 0x9fff ../unifont/unifont.9800-9FFF
+0xa000 0xa7ff ../unifont/unifont.A000-A7FF
+0xa800 0xafff ../unifont/unifont.A800-AFFF
+0xb000 0xb7ff ../unifont/unifont.B000-B7FF
+0xb800 0xbfff ../unifont/unifont.B800-BFFF
+0xc000 0xc7ff ../unifont/unifont.C000-C7FF
+0xc800 0xcfff ../unifont/unifont.C800-CFFF
+0xd000 0xd7ff ../unifont/unifont.D000-D7FF
+0xf900 0xfffc ../unifont/unifont.F900-FFFC
+0x10000 0x107ff ../unifont/unifont.10000-107FF
+0x10800 0x10fff ../unifont/unifont.10800-10FFF
+0x11000 0x117ff ../unifont/unifont.11000-117FF
+0x11800 0x11fff ../unifont/unifont.11800-11FFF
+0x1239a 0x123ff ../unifont/unifont.1239A-123FF
+0x1246f 0x1246f ../unifont/unifont.1246F-1246F
+0x12475 0x1247f ../unifont/unifont.12475-1247F
+0x12544 0x12d43 ../unifont/unifont.12544-12D43
+0x12d44 0x12fff ../unifont/unifont.12D44-12FFF
+0x1342f 0x13c2e ../unifont/unifont.1342F-13C2E
+0x13c2f 0x143ff ../unifont/unifont.13C2F-143FF
+0x14647 0x14e46 ../unifont/unifont.14647-14E46
+0x14e47 0x15646 ../unifont/unifont.14E47-15646
+0x15647 0x15e46 ../unifont/unifont.15647-15E46
+0x15e47 0x16646 ../unifont/unifont.15E47-16646
+0x16647 0x167ff ../unifont/unifont.16647-167FF
+0x16a39 0x16fff ../unifont/unifont.16A39-16FFF
+0x187f2 0x187ff ../unifont/unifont.187F2-187FF
+0x18af3 0x192f2 ../unifont/unifont.18AF3-192F2
+0x192f3 0x19af2 ../unifont/unifont.192F3-19AF2
+0x19af3 0x1a2f2 ../unifont/unifont.19AF3-1A2F2
+0x1a2f3 0x1aaf2 ../unifont/unifont.1A2F3-1AAF2
+0x1aaf3 0x1b2f2 ../unifont/unifont.1AAF3-1B2F2
+0x1b2f3 0x1baf2 ../unifont/unifont.1B2F3-1BAF2
+0x1baf3 0x1c2f2 ../unifont/unifont.1BAF3-1C2F2
+0x1c2f3 0x1caf2 ../unifont/unifont.1C2F3-1CAF2
+0x1caf3 0x1d2f2 ../unifont/unifont.1CAF3-1D2F2
+0x1d2f3 0x1daf2 ../unifont/unifont.1D2F3-1DAF2
+0x1daf3 0x1e2f2 ../unifont/unifont.1DAF3-1E2F2
+0x1e2f3 0x1eaf2 ../unifont/unifont.1E2F3-1EAF2
+0x1eaf3 0x1f2f2 ../unifont/unifont.1EAF3-1F2F2
+0x1f2f3 0x1faf2 ../unifont/unifont.1F2F3-1FAF2
+0x1faf3 0x1fffd ../unifont/unifont.1FAF3-1FFFD
+0xe0000 0xe007f ../unifont/unifont.E0000-E007F
+0xe0100 0xe01ee ../unifont/unifont.E0100-E01EE
+0xe01ef 0xe01ef ../unifont/unifont.E01EF-E01EF
0xfff9 0xffff ../dejavu/dejavu.12.fff9
0xfb00 0xfc00 ../dejavu/dejavu.12.fb00
0xf6c5 0xf7c5 ../dejavu/dejavu.12.f6c5
prev parent reply other threads:[~2022-09-23 2:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 16:44 mag-one
2022-09-22 17:29 ` Sigrid Solveig Haflínudóttir
2022-09-23 2:47 ` ori [this message]
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=0A519E28E1E2009FE5F5C84F18C93390@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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 NNTP newsgroup(s).