From: "Philip Silva via 9fans" <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] netsurf or opossum
Date: Mon, 03 May 2021 20:45:48 +0000 [thread overview]
Message-ID: <i0DT5ABEUmmjmfNL9o6-pjx2Ei-S13EtxiApyTK1-T8anYM8F8tbK_aW4CZ5QXKw0SvdcIPHPqnSwHCNK6ydBnZCK90W2hObsXteqCte9qs=@protonmail.com> (raw)
In-Reply-To: <F2AB834CF660547BAC0F46ECD75B4FE0@eigenstate.org>
Hi!
Here's a patch for most of the fullwidth glyphs in lucidasans and vga! The subfonts are already used in each font file. I guess one way to quickly test would be:
hget https://ja.wikipedia.org | htmlfmt > /tmp/wp
for (font in /lib/font/bit/lucidasans/unicode.*.font /lib/font/bit/vga/unicode.font) {
acme /tmp/wp
}
Probably a similar patch could also easily be created for the bold and italic versions, but that's too much work for now :)
Philip
diff -r 859a4e61471b lib/font/bit/lucidasans/unicode.10.font
--- a/lib/font/bit/lucidasans/unicode.10.font Mon May 03 21:04:39 2021 +0200
+++ b/lib/font/bit/lucidasans/unicode.10.font Mon May 03 22:35:32 2021 +0200
@@ -55,6 +55,7 @@
0x9a01 0x9bf5 ../shinonome/k16.9a01
0x9c04 0x9dfd ../shinonome/k16.9c04
0x9e1a 0x9fa0 ../shinonome/k16.9e1a
+0xff01 0xffe5 ../shinonome/k16.ff01
0xfb1e 0xfb1e ../lucida/Althebrew.9.0
0xfff9 0xffff ../dejavu/dejavu.16.fff9
0xfb00 0xfc00 ../dejavu/dejavu.16.fb00
diff -r 859a4e61471b lib/font/bit/lucidasans/unicode.13.font
--- a/lib/font/bit/lucidasans/unicode.13.font Mon May 03 21:04:39 2021 +0200
+++ b/lib/font/bit/lucidasans/unicode.13.font Mon May 03 22:35:32 2021 +0200
@@ -56,3 +56,4 @@
0x9c00 0x9dff ../jis/jis9c00.24
0x9e00 0x9fff ../jis/jis9e00.24
0xfb1e 0xfb1e ../lucida/Althebrew.12.0
+0xfee0 0xff5e lsr.24
diff -r 859a4e61471b lib/font/bit/lucidasans/unicode.6.font
--- a/lib/font/bit/lucidasans/unicode.6.font Mon May 03 21:04:39 2021 +0200
+++ b/lib/font/bit/lucidasans/unicode.6.font Mon May 03 22:35:32 2021 +0200
@@ -56,6 +56,7 @@
0x9a01 0x9bf5 ../shinonome/k12.9a01
0x9c04 0x9dfd ../shinonome/k12.9c04
0x9e1a 0x9fa0 ../shinonome/k12.9e1a
+0xff01 0xffe5 ../shinonome/k12.ff01
0xfb00 0xfbff ../fixed/6x12.FB00
0xfe00 0xfeff ../fixed/6x12.FE00
0xff00 0xffff ../fixed/6x12.FF00
diff -r 859a4e61471b lib/font/bit/lucidasans/unicode.7.font
--- a/lib/font/bit/lucidasans/unicode.7.font Mon May 03 21:04:39 2021 +0200
+++ b/lib/font/bit/lucidasans/unicode.7.font Mon May 03 22:35:32 2021 +0200
@@ -59,6 +59,7 @@
0x9a01 0x9bf5 ../shinonome/k12.9a01
0x9c04 0x9dfd ../shinonome/k12.9c04
0x9e1a 0x9fa0 ../shinonome/k12.9e1a
+0xff01 0xffe5 ../shinonome/k12.ff01
0xfb00 0xfbff ../fixed/7x14.FB00
0xff00 0xffff ../fixed/7x14.FF00
0x0600 0x06ff ../fixed/9x15.0600
diff -r 859a4e61471b lib/font/bit/lucidasans/unicode.8.font
--- a/lib/font/bit/lucidasans/unicode.8.font Mon May 03 21:04:39 2021 +0200
+++ b/lib/font/bit/lucidasans/unicode.8.font Mon May 03 22:35:32 2021 +0200
@@ -66,6 +66,7 @@
0x9a01 0x9bf5 ../shinonome/k14.9a01
0x9c04 0x9dfd ../shinonome/k14.9c04
0x9e1a 0x9fa0 ../shinonome/k14.9e1a
+0xff01 0xffe5 ../shinonome/k14.ff01
0xfb00 0xfbff ../fixed/9x18.FB00
0xfe00 0xfeff ../fixed/9x18.FE00
0xff00 0xffff ../fixed/9x18.FF00
diff -r 859a4e61471b lib/font/bit/vga/unicode.font
--- a/lib/font/bit/vga/unicode.font Mon May 03 21:04:39 2021 +0200
+++ b/lib/font/bit/vga/unicode.font Mon May 03 22:35:32 2021 +0200
@@ -191,6 +191,7 @@
0x9a01 0x9bf5 ../shinonome/k12.9a01
0x9c04 0x9dfd ../shinonome/k12.9c04
0x9e1a 0x9fa0 ../shinonome/k12.9e1a
+0xff01 0xffe5 ../shinonome/k12.ff01
0x0e00 0x0eff ../fixed/7x14.0E00
0x1600 0x16ff ../fixed/7x14.1600
0x2400 0x24ff ../fixed/7x14.2400
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
Am Montag, 26 April 2021 21:29 schrieb <ori@eigenstate.org>:
> Yes, that seems like a font issue, and should be fixed there.
> I'll gladly commit patches that fix missing glyphs.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T9a725c37f61954a8-M868b7e06206f0a22d9fdd868
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-05-03 20:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 6:52 kokamoto
2021-01-07 8:07 ` Lucio De Re
2021-01-07 8:28 ` Mark van Atten
2021-01-07 20:50 ` Philip Silva via 9fans
2021-01-07 23:24 ` kokamoto
2021-01-08 5:48 ` kokamoto
2021-04-22 1:34 ` kokamoto
2021-04-22 7:36 ` Philip Silva via 9fans
2021-04-22 7:39 ` Philip Silva via 9fans
2021-04-23 4:37 ` kokamoto
2021-04-23 13:10 ` Philip Silva via 9fans
2021-04-24 0:18 ` kokamoto
2021-04-24 2:00 ` kokamoto
2021-04-24 15:51 ` Philip Silva via 9fans
2021-04-25 4:07 ` kokamoto
2021-04-26 18:25 ` Philip Silva via 9fans
2021-04-26 19:29 ` ori
2021-05-03 20:45 ` Philip Silva via 9fans [this message]
2021-05-04 0:56 ` kokamoto
2021-05-04 4:11 ` kokamoto
2021-05-04 4:14 ` kokamoto
2021-05-08 10:12 ` Philip Silva via 9fans
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='i0DT5ABEUmmjmfNL9o6-pjx2Ei-S13EtxiApyTK1-T8anYM8F8tbK_aW4CZ5QXKw0SvdcIPHPqnSwHCNK6ydBnZCK90W2hObsXteqCte9qs=@protonmail.com' \
--to=9fans@9fans.net \
/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).