Sujet : Re: Rationale for aligning data on even bytes in a Unix shell file?
De : Bonita.Montero (at) *nospam* gmail.com (Bonita Montero)
Groupes : comp.lang.cDate : 28. Apr 2025, 17:56:16
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vuobu5$3o38b$2@raubtier-asyl.eternal-september.org>
References : 1 2 3 4 5 6 7 8 9 10 11 12
User-Agent : Mozilla Thunderbird
Am 28.04.2025 um 16:24 schrieb Scott Lurndal:
Bonita Montero <Bonita.Montero@gmail.com> writes:
Am 28.04.2025 um 11:39 schrieb Bonita Montero:
>
Am 28.04.2025 um 11:31 schrieb Muttley@DastardlyHQ.org:
>
Yes, Unix-APIs are really achaic. When you have a filename written
with ohne user's locale and another with a different locale reads
that he get's at most a partitially readable filename. For Janis
this seems to be flexibility, but for me that's a problem. A file-
system should have fixed charset, at best Unicode.
>
I did have a look at how macOS / APFS handles this:
for macOS all filenames are UTF-8.
No, unix (and macOS _is_ unix) filenames are a simple stream of
bytes with no meaning or semantic associated with the bytes other than the
terminating nul character and the directory separator character.
The Wikipedia says that APFS is UTF-8 capable.
https://en.wikipedia.org/wiki/Apple_File_System