Rocksolid Light

News from da outaworlds

mail  files  register  groups  login

Message-ID:  

BOFH excuse #150: Arcserve crashed the server again.

comp / comp.unix.shell / Re: Font support for utf8

SubjectAuthor
* Font support for utf8Richard Harnden
+* Re: Font support for utf8John McCue
|`- Re: Font support for utf8Keith Thompson
`- Re: Font support for utf8Lawrence D'Oliveiro

1
Subject: Font support for utf8
From: Richard Harnden
Newsgroups: comp.unix.shell
Organization: A noiseless patient Spider
Date: Fri, 20 Dec 2024 13:55 UTC
Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: richard.nospam@gmail.invalid (Richard Harnden)
Newsgroups: comp.unix.shell
Subject: Font support for utf8
Date: Fri, 20 Dec 2024 13:55:18 +0000
Organization: A noiseless patient Spider
Lines: 9
Message-ID: <vk3t09$3fcrp$1@dont-email.me>
Reply-To: nospam.harnden@invalid.com
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 20 Dec 2024 14:55:21 +0100 (CET)
Injection-Info: dont-email.me; posting-host="6588eeb2e27a2b3b9afaf93791cb9d67";
logging-data="3650425"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19wRR11aqLOrupebJmBlp7D0PQnPozs724="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:9iCt7J676f46xmE5VdALgugj36s=
Content-Language: en-US
View all headers

Hi,

Is there anyway I can tell whether a particular uft8 code-point is
actually implemented in my terminal's current font?

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

Thanks.

Subject: Re: Font support for utf8
From: John McCue
Newsgroups: comp.unix.shell
Organization: A noiseless patient Spider
Date: Fri, 20 Dec 2024 15:14 UTC
References: 1
Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: jmccue@qball.jmcunx.com (John McCue)
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
View all headers

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

Subject: Re: Font support for utf8
From: Keith Thompson
Newsgroups: comp.unix.shell
Organization: None to speak of
Date: Fri, 20 Dec 2024 18:57 UTC
References: 1 2
Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Keith.S.Thompson+u@gmail.com (Keith Thompson)
Newsgroups: comp.unix.shell
Subject: Re: Font support for utf8
Date: Fri, 20 Dec 2024 10:57:54 -0800
Organization: None to speak of
Lines: 25
Message-ID: <87jzbuw5al.fsf@nosuchdomain.example.com>
References: <vk3t09$3fcrp$1@dont-email.me> <vk41km$3gcqo$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 20 Dec 2024 19:57:55 +0100 (CET)
Injection-Info: dont-email.me; posting-host="02872b6dfbe0db08082cdbb7f2d2a958";
logging-data="3763686"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/3gLfBhuDribM1ZZOm+CUR"
User-Agent: Gnus/5.13 (Gnus v5.13)
Cancel-Lock: sha1:01rnNKrmKDe4ksunCFNFk0cF7YU=
sha1:ytPiGO+JLerArnBeIu6ibwg5Rec=
View all headers

John McCue <jmccue@qball.jmcunx.com> writes:
> Richard Harnden <richard.nospam@gmail.invalid> wrote:
>> 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.

That's a function of which font you're using. I'm using xterm with
the Inconsolata font, which does have good UTF-8 support, including
the LEFT SEVEN EIGHTHS BLOCK character. Any program should display
it correctly if you use a font that knows how to display it (assuming
the program itself handles UTF-8).

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */

Subject: Re: Font support for utf8
From: Lawrence D'Oliv
Newsgroups: comp.unix.shell
Organization: A noiseless patient Spider
Date: Fri, 20 Dec 2024 20:50 UTC
References: 1
Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: ldo@nz.invalid (Lawrence D'Oliveiro)
Newsgroups: comp.unix.shell
Subject: Re: Font support for utf8
Date: Fri, 20 Dec 2024 20:50:04 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 15
Message-ID: <vk4l9s$3k7iv$8@dont-email.me>
References: <vk3t09$3fcrp$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 20 Dec 2024 21:50:05 +0100 (CET)
Injection-Info: dont-email.me; posting-host="adef4b4b089501c29b0b319666d85569";
logging-data="3808863"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19lIZtfK2VYM5pmJazeN2Nr"
User-Agent: Pan/0.161 (Chasiv Yar; )
Cancel-Lock: sha1:bdJeIagBFaY6tSme3XmkMKnoo0I=
View all headers

On Fri, 20 Dec 2024 13:55:18 +0000, Richard Harnden wrote:

> Is there anyway I can tell whether a particular uft8 code-point is
> actually implemented in my terminal's current font?

You need some utility to dump out the font’s character-mapping table.

E.g. I wrote a Python script called “code_coverage” here
<https://gitlab.com/ldo/python_freetype_examples/>, which will list
the code blocks defined for any specified font.

In this repo <https://gitlab.com/ldo/python_fontconfig_examples/>,
there is a tool called “coverage_list”. This will scan all the fonts
that fontconfig on your system knows about, to find those that cover a
given code block.

1

rocksolid light 0.9.8
clearnet tor