Warning: mysqli::__construct(): (HY000/1203): User howardkn already has more than 'max_user_connections' active connections in D:\Inetpub\vhosts\howardknight.net\al.howardknight.net\includes\artfuncs.php on line 21
Failed to connect to MySQL: (1203) User howardkn already has more than 'max_user_connections' active connectionsPath: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Rich Newsgroups: comp.os.linux.misc Subject: Re: Case Insensitive File Systems -- Torvalds Hates Them Date: Tue, 3 Jun 2025 11:41:34 -0000 (UTC) Organization: A noiseless patient Spider Lines: 55 Message-ID: <101mn1e$3vdni$1@dont-email.me> References: <101gt61$1s439$2@dont-email.me> <101j4nq$2udcb$2@dont-email.me> <101jq1q$36qt0$1@dont-email.me> <101jur7$386sv$1@dont-email.me> <101mfd2$3tnqt$2@dont-email.me> Injection-Date: Tue, 03 Jun 2025 13:41:36 +0200 (CEST) Injection-Info: dont-email.me; posting-host="88c237dffc5f2108540b2ddbced93531"; logging-data="4175602"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18fH34+bcJAxptwxwSl+s2+" User-Agent: tin/2.6.1-20211226 ("Convalmore") (Linux/5.15.139 (x86_64)) Cancel-Lock: sha1:sv6sKacYE+7T/dpIuJ0cZcdh1G0= Nuno Silva wrote: > On 2025-06-02, Rich wrote: > >> Nuno Silva 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...), A suggestion: hardware terminals (yes, redundant if one defines "terminal" to mean hardware terminal, but does remove the ambiguity with "virtual terminals"). > 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.) Given that any existing hardware terminals are very likely going to predate the very concept of unicode and utf-8 encoding, they are likely to be very limited in their supported character sets and glyphs. > 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. You very well may be one of only a handful of folks left to even have a hardware terminal setup and operational.