Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.os.linux.misc Subject: Re: Case Insensitive File Systems -- Torvalds Hates Them Date: Mon, 2 Jun 2025 03:10:50 -0000 (UTC) Organization: A noiseless patient Spider Lines: 10 Message-ID: <101j4nq$2udcb$2@dont-email.me> References: <20250428080014.0000347f@gmail.com> <20250428111242.00007426@gmail.com> <101gt61$1s439$2@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Mon, 02 Jun 2025 05:10:50 +0200 (CEST) Injection-Info: dont-email.me; posting-host="a67f84b66e6f22f56d2f18bad75708af"; logging-data="3093899"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/VmHeu7ngIt2WX7C5jfflZ" User-Agent: Pan/0.162 (Pokrosvk) Cancel-Lock: sha1:nVcU6XQvEYUiaDbiyjdF7ArmdRE= 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.