Re: Rationale for aligning data on even bytes in a Unix shell file?

On 2025-04-28, Michael S <already5chosen@yahoo.com> wrote:

On Mon, 28 Apr 2025 18:28:46 -0000 (UTC)
Kaz Kylheku <643-408-1753@kylheku.com> wrote:
>

On 2025-04-28, Michael S <already5chosen@yahoo.com> wrote:

>
That's nonsense.
Every case-preserving case-insensitive file system has to understand
characters encoding, at least to a certain degree. 

 
Commonly used filesystems on Linux are case sensitive.
 

>
Scott's claim was about *all* Unixes and in his previous message he
emphasized that he classifies Apple OS/X as Unix.

Apple breaks Unix in some deranged attempt to second-guess
what is good for "the rest of them".

This issue is no longer relevant to users in 2025. Users do not
type entire filenames from scratch in order to open files. They
click on things, or possibly use search/completion.

It is the application level file search features that need to pander to
issues like case insensitivity.

Case sensitivity means that a user could create a file "Foo.png" and
another "foo.PNG", and then have them appear in the folder side by side.
Well, big whoopty whoop. They can double click on either of them to see
what it is. They are not gonna type the name to do that! If they don't
like it that there are two files with similar names they can click on
either name, and change it.

Now when the user searches for "foo", or for PNG files the finder should
find both files. But that doesn't require the filesystem to be case
insensitive, only the search logic in the finder. That's where you can
go to town with supporting Unicode normalization and whatnot.


--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca