4 ms·

I just tested and my local nerdfont[1] does not support a bunch of those graphical glyphs, perhaps that is something that could be added. [1] https://www.nerdf

• otikik 10mo ago
  https://github.com/ryanoasis/nerd-fonts/issues/1959 https://github.com/ryanoasis/nerd-fonts/issues/1959
  • zimpenfish 10mo ago
    Thanks for filing that. I was slightly confused by the appearance of the red race car.
• anthk 10mo ago
  Nerdfont sucks as it's non-standard.
  • otikik 10mo ago
    Why is that important?
    • anthk 10mo ago
      It deviates from the Unicode standard. It's doomed to fail.
      • otikik 10mo ago
        Everything in life is temporary. If it lasts while I use it, it's as good to me as if it lasts forever.
        • anthk 10mo ago
          ASCII and Unicode will outlast us. Not the case with Nerd fonts.
          • kragen 10mo ago
            Hopefully the people after us will spend some time enjoying the things we have left to them; if they dedicate all their time to creating things that will outlast them, all our efforts will have been wasted.
          • otikik 10mo ago
            If it lasts 10 years, it's good enough for me.
      • Ycros 10mo ago
        there's enough support for it across various things that it's not going anywhere
        • anthk 10mo ago
          They said the same about ISO-8859-* encodings, Webdings/Windings fonts under Windows. Gone. Forever.
          • kragen 10mo ago
            Wingdings is available in OTF format to put on your web site as a webfont: https://www.onlinewebfonts.com/fonts/wingdings_OTF https://www.onlinewebfonts.com/fonts/wingdings_OTF So is Webdings: https://www.dafontfree.io/webdings-font/ 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 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.
            • anthk 10mo ago
              >Webdings even got integrated into Unicode 7.0, That's the point. Think again.
              • kragen 10mo ago
                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.
                • anthk 10mo ago
                  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.
• krackout 10mo ago
  I got incredibly accurate output on my terminal emulator using a nerd font (st with Iosevka Nerd Font, tmux, links2 browser). Out of curiosity I checked with lsof, apparently other fonts are used as fallback: /usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf /usr/share/fonts/truetype/droid/DroidSansFallbackFull.ttf /usr/local/share/fonts/MS/segmdl2.ttf /usr/local/share/fonts/MS/seguisym.ttf /usr/local/share/fonts/nerd/Iosevka/IosevkaNerdFont-Regular.ttf /usr/local/share/fonts/nerd/JetBrainsMono/JetBrainsMonoNerdFontMono-Regular.ttf At least the result is perfect!