Re: Case Insensitive File Systems -- Torvalds Hates Them

On 2025-06-02, Rich wrote:

Nuno Silva <nunojsilva@invalid.invalid> wrote:

On 2025-06-02, Lawrence D'Oliveiro wrote:
 

On Sun, 01 Jun 2025 07:49:37 +0100, Nuno Silva wrote:
>

This also introduces a problem where the character you propose
requires support to display.  With ASCII, one can be reasonably
confident that a lot of interfaces will be able to display it.  But
that char (like the curly quotes you use?) becomes an accessibility
issue once the information has to be displayed on, say, a latin1
terminal (or rather: a terminal that can't do UCS).

>
Everything does Unicode nowadays.

 
I have never seen a Unicode-capable terminal myself, and, while I've
not done much sampling, I doubt they're in any way common or
frequent.

>
urxvt -- using it right now.
>
https://www.linuxlinks.com/urxvt/
>
Note that to actually display characters your font files do need glyphs
for the codepoints you are trying to display.  But a font lacking a
glyph for a given codepoint is not urxvt's fault.

For terminals (the hardware devices, it seems we may need to get another
word for terminals, as it might otherwise be seen as nitpicking...),
another issue is likely to be that, even if it somehow can support utf8,
it might be limited in how much glyphs it can support at once. (I mean,
not by an incomplete font, but because it has a limit in how much glyphs
any font can have.)


There'll be terminals with at least some graphical capability, but
that's only usable if it's fast enough.

I think mine supports changing fonts, but unless the customization is
done with a cartridge(?) on the back side, I suspect loading the
customization will not be very fast.

--
Nuno Silva