Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Janis Papanagnou <janis_papanagnou+ng@hotmail.com>
Newsgroups: comp.lang.c
Subject: Re: Rationale for aligning data on even bytes in a Unix shell file?
Date: Thu, 8 May 2025 12:52:36 +0200
Organization: A noiseless patient Spider
Lines: 26
Message-ID: <vvi2dm$1ni4e$1@dont-email.me>
References: <vuih43$2agfa$1@dont-email.me> <vuml73$1riea$1@dont-email.me>
 <vun04h$2fjrn$2@raubtier-asyl.eternal-september.org>
 <vun1nh$22hc5$3@dont-email.me>
 <vunak2$2p980$1@raubtier-asyl.eternal-september.org>
 <vunbgo$2q5u8$1@dont-email.me>
 <vunbjg$2q72n$1@raubtier-asyl.eternal-september.org>
 <vund1f$2rh3j$1@dont-email.me>
 <vungko$2uoa2$1@raubtier-asyl.eternal-september.org>
 <X9MPP.1383458$f81.819466@fx48.iad>
 <vuobri$3o38b$1@raubtier-asyl.eternal-september.org>
 <XtOPP.2986761$t84d.2537581@fx11.iad>
 <vuohq9$3tlhf$1@raubtier-asyl.eternal-september.org>
 <vuoig5$3ub4j$1@dont-email.me>
 <vuorpf$6tnn$1@raubtier-asyl.eternal-september.org>
 <vup2nt$bi1k$2@dont-email.me>
 <vupofl$13pg2$2@raubtier-asyl.eternal-september.org>
 <vuprce$15sqo$2@dont-email.me>
 <vvd6n5$353gs$1@raubtier-asyl.eternal-september.org>
 <vvfbnj$ulpc$1@dont-email.me> <vvflec$11b72$1@dont-email.me>
 <vvg8uq$1647n$2@dont-email.me> <vvghrg$18321$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 08 May 2025 12:52:41 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="68c32824e17de1f129cf89596dd3462d";
	logging-data="1820814"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19TVZzP/44TLevoReqLFFUx"
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101
 Thunderbird/45.8.0
Cancel-Lock: sha1:ltyWLqWUzOHrds48YuIjICW2MBY=
In-Reply-To: <vvghrg$18321$1@dont-email.me>
X-Enigmail-Draft-Status: N1110
Bytes: 3198

On 07.05.2025 23:03, David Brown wrote:
>> [...]
> 
> No matter how you choose to do it, you will get it wrong sometimes.
> Case-insensitive comparison has language-specific details in addition to
> the character in the Unicode tables.  Should the lower-case version of
> "SS" be "ss" or "ß" ?  That depends on the language and the position of
> the letters.  Should the capital of "ß" be "SS" or "ẞ"?  [...]

Concerning file system's named directory entries - and I'm speaking
for German here - an "ß" is not the same as an "ss" or "sz" ligature.
An "ss" for example may either be part of an ordinary word or just a
"replacement representation" (I'm lacking the correct English term)
for the 'Sharp S'. So the letters shall not be substituted by other
letters (or letter sequences) but always taken literally. So an "SS"
shall always be "ss". Historically the only relevant problem was the
'Lower Case Sharp S' where there had been no 'Upper Case Sharp S',
but that situation has changed (not too long ago).

The main point of issues with "flattening" cases in case-insensitive
(file-)systems is still undisputed [by me] of course.

Janis

> [...]