Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: John McCue <jmccue@qball.jmcunx.com>
Newsgroups: comp.unix.shell
Subject: Re: Font support for utf8
Date: Fri, 20 Dec 2024 15:14:30 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 22
Message-ID: <vk41km$3gcqo$1@dont-email.me>
References: <vk3t09$3fcrp$1@dont-email.me>
Reply-To: jmclnx@SPAMisBADgmail.com
Injection-Date: Fri, 20 Dec 2024 16:14:30 +0100 (CET)
Injection-Info: dont-email.me; posting-host="4430a1da82415cb58dd0bb82b1896fd5";
	logging-data="3683160"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18KbZacYTjSf98j0/Qt4/RC"
User-Agent: tin/2.6.3-20231224 ("Banff") (OpenBSD/7.6 (amd64))
Cancel-Lock: sha1:NeMEN6tpGE3fe0H+E2h1WoBXejY=
X-OS-Version: OpenBSD 7.6 amd64
Bytes: 1629

Richard Harnden <richard.nospam@gmail.invalid> wrote:
> Hi,
> 
> Is there anyway I can tell whether a particular uft8 code-point is 
> actually implemented in my terminal's current font?

The only way I know is to write a small program to
print it.  That is what I did for various UTF-8
characters I like to use.

> For example, 0xe2 0x96 0x89 "?" "Left Seven Eighths Block" is often 
> displayed as the i-don't-know-what-this-is glyph.

FWIW, 7/8 does not print for me on Linux and *BSD, but
on all systems Emacs will print it plus many more that
does not show up on xterm and other terms.

> Thanks.

-- 
csh(1) - "An elegant shell, for a more... civilized age."
                     - Paraphrasing Star Wars