Hacker News Reader

Comment by Ycros | Hacker News Reader

there's enough support for it across various things that it's not going anywhere

They said the same about ISO-8859-* encodings, Webdings/Windings fonts under Windows. Gone. Forever.

Wingdings is available in OTF format to put on your web site as a webfont: https://www.onlinewebfonts.com/fonts/wingdings_OTF

So is Webdings: https://www.dafontfree.io/webdings-font/

Webdings even got integrated into Unicode 7.0, so all the Noto fonts support it: https://en.wikipedia.org/wiki/Webdings

And recode(1) has full support for ISO-8859-*. As does iconv and the Python3 encodings.codecs module. I'm pretty sure browsers can render pages in them, too. Firefox keeps rendering UTF-8 pages as if they were ISO-8859-1 encoded when I screw up at setting the charset parameter on their content-type.

>Webdings even got integrated into Unicode 7.0,

That's the point. Think again.

It seems incompatible with the idea that it's "Gone. Forever." Thinking again doesn't change that for me. The only thing that's gone is the exclusivity to a single proprietary-software vendor.

A simple case. Amigans can still use thanks to standards, Usenet and IRC, they can connect to Bitlbee.org to several choices. With Discord and such it's more difficult, but for Jabber there's no isue at all. Ditto with AmiSSL and Jabber, Gemini clients. They can reuse Amiga 4000 machines (or FPGA based ones) and browse small sites, Gopher, connect to Biltbee and make tons of services usable again.

With Nerdfonts, these will be obsolete in further Unicode releases.

GNU Unifont and the unicode table might be backported to the Amiga. With NerdFonts, you need to do twice the jobs.

Reply on news.ycombinator.com