C++ Logo


Advanced search

Re: [SG16-Unicode] It???s Time to Stop Adding New Features for Non-Unicode Execution Encodings in C++

From: Tom Honermann <tom_at_[hidden]>
Date: Tue, 30 Apr 2019 10:49:50 -0400
On 4/29/19 6:32 PM, Thiago Macieira wrote:
> On Monday, 29 April 2019 10:53:26 PDT keld_at_[hidden] wrote:
>>> Operating systems that are encoding independent are mostly a myth at this
>>> point. Probably always were. Linux is mostly utf-8, Osx is Unicode,
>>> windows
>>> is slowly getting there etc.
>> linux still is,
> Still a myth that it's encoding-independent. Just insert a VFAT- or NTFS-
> formatted USB stick and you'll have your kernel assuming your userspace is
> UTF-8. You can change it, by supplying mount options when mounting said
> filesystem, but most users don't and don't even know such options exist.

Can you elaborate on this? What do you mean by the "kernel assuming
your userspace is UTF-8"? Do you mean that the filesystem driver will
attempt to, by default, present file names composed of 16-bit code units
transcoded to UTF-8 by default? Given that file names do not have an
explicit encoding, this seems reasonable to me and even necessary to
avoid name conflicts from otherwise lossy transcoding operations.


Received on 2019-04-30 16:49:53