Comment by dspillett
14 hours ago
That method isn't entirely reliable either: all come out at “question mark in a box” (Chrome, Edge) or “codepoint hex in box” (FF) on the old Win10 box that I'm currently trying to retire. The come out find on a similarly default Win11 setup.
While the issue here is Win10, it shows that the problem is client font sensitive so it might affect others too (perhaps those running old-but-still-supported Linux distro releases with default fonts).
> all come out at “question mark in a box” (Chrome, Edge) or “codepoint hex in box” (FF) on the old Win10 box that I'm currently trying to retire. The come out find on a similarly default Win11 setup.
This is pretty funny to me, because on plain ol' Firefox on NixOS everything looks just fine!
We've come pretty far from the days when things were randomly broken on Linux..
Firefox on Fedora 43 here, no joy, and indeed, randomly broken on Linux (too).
[edit] Okey, so installing the complete Google Noto Fonts family resolved this issue. But I still don't know if relying on a script with almost no font support is any better than what the OP did.