From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ttf2subf
Date: Wed, 22 Mar 2006 18:52:59 -0800 [thread overview]
Message-ID: <512749669ac705f04b4f83eec521cfb9@collyer.net> (raw)
In-Reply-To: <a6378e7cbe484c2b7ff803d654df0e04@swtch.com>
Even /lib/font/bit/lucm/unicode.9.font has good but not perfect
coverage. I've stumbled over occasional missing glyphs. Some
alphabets are missing (I'll have to look later to find out which) and
some non-letters too. Here's are some examples:
; uniquery check
2447 ⑇
2611 ☑
2713 ✓
2714 ✔
; uniquery slash
2044 ⁄
20e0 ⃠
2215 ∕
2298 ⊘
233f ⌿
2340 ⍀
2341 ⍁
2342 ⍂
2349 ⍉
244a ⑊
; uniquery point
00ab «
00bb »
05b0 ְ
05b1 ֱ
05b2 ֲ
05b3 ֳ
05b4 ִ
05b5 ֵ
05b6 ֶ
05b7 ַ
05b8 ָ
05b9 ֹ
05bb ֻ
05bc ּ
05bd ֽ
05bf ֿ
05c1 ׁ
05c2 ׂ
066d ٭
2027 ‧
2039 ‹
203a ›
2041 ⁁
2329 〈
232a 〉
25b2 ▲
25b3 △
25b4 ▴
25b5 ▵
25b6 ▶
25b7 ▷
25b8 ▸
25b9 ▹
25ba ►
25bb ▻
25bc ▼
25bd ▽
25be ▾
25bf ▿
25c0 ◀
25c1 ◁
25c2 ◂
25c3 ◃
25c4 ◄
25c5 ◅
25ec ◬
25ed ◭
25ee ◮
261a ☚
261b ☛
261c ☜
261d ☝
261e ☞
261f ☟
2726 ✦
2727 ✧
2734 ✴
2735 ✵
2736 ✶
2737 ✷
2738 ✸
2739 ✹
273a ✺
2742 ❂
279b ➛
27a8 ➨
333d ㌽
fb1e ﬞ
; cat /bin/uniquery
#!/bin/rc
# uniquery pattern... - print hex & glyph of any chars matching pattern
# in /lib/unicode
sts=''
for (pat) {
hexes = `{grep $pat /lib/unicode | column 1}
if (~ $#hexes 0) {
echo $0: no such unicode chars: $pat >[1=2]
sts='no such chars'
}
if not
for (hex in $hexes)
unicode $hex-$hex
}
exit $sts
next prev parent reply other threads:[~2006-03-23 2:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-23 2:29 erik quanstrom
2006-03-23 2:35 ` andrey mirtchovski
2006-03-23 2:38 ` Russ Cox
2006-03-23 2:52 ` geoff [this message]
2006-03-23 3:00 ` andrey mirtchovski
2006-03-23 3:06 ` andrey mirtchovski
2006-03-23 10:40 ` Arvindh Rajesh Tamilmani
-- strict thread matches above, loose matches on Subject: below --
2006-03-23 3:57 erik quanstrom
2006-03-23 4:36 ` Russ Cox
2006-03-23 7:58 ` Bruce Ellis
2006-03-23 11:38 ` erik quanstrom
2006-03-23 14:32 ` Russ Cox
2006-03-23 3:20 erik quanstrom
2006-03-23 3:33 ` Russ Cox
2006-03-23 2:51 erik quanstrom
2006-03-23 2:57 ` Russ Cox
2006-03-23 2:34 erik quanstrom
2006-03-23 4:31 ` Latchesar Ionkov
2006-03-23 2:03 erik quanstrom
2006-03-23 2:27 ` Latchesar Ionkov
2006-03-23 10:18 ` Charles Forsyth
2006-03-23 21:38 ` Tim Wiess
2006-03-23 0:12 erik quanstrom
2006-03-23 0:45 ` andrey mirtchovski
2006-03-23 2:25 ` Russ Cox
2006-03-23 2:33 ` Latchesar Ionkov
2005-05-05 3:06 andrey mirtchovski
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=512749669ac705f04b4f83eec521cfb9@collyer.net \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
/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).