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

scott@slp53.sl.home (Scott Lurndal) writes:

Bonita Montero <Bonita.Montero@gmail.com> writes:
>

Am 29.04.2025 um 02:28 schrieb Scott Lurndal:
>

Bonita Montero <Bonita.Montero@gmail.com> writes:
>

Am 28.04.2025 um 20:47 schrieb Richard Harnden:
>

On 28/04/2025 19:36, Bonita Montero wrote:
>

Am 28.04.2025 um 18:59 schrieb Scott Lurndal:
>

Not really.  UTF-8 is UTF-8, regardless of the locale.

>
But UTF-8 isn't the standard locale for Unix filesystems
except with macOS.

>
UTF-8 isn't a locale - it's an encoding.

>
Idiot.
Type "locale" in the shell and thenn return.

>
$ locale
LANG=C
LC_CTYPE="C"
LC_NUMERIC=C
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=

>
For me:
>
boni@Raubtier-Asyl:/mnt/c/Users/Boni$ locale
LANG=C.UTF-8
LANGUAGE=

>
Same locale, different encoding.   As has been pointed out
to you repeatedly.

I don't want to take sides in this exchange, but I feel obliged to
point out that, in the terminology of the ISO C standard, having a
different encoding implies being a different locale.  So it might be
good to specify a frame of reference for where the term "locale" has
its source, for the various respective comments being offered.