> On 27 Nov 2017, at 22:51, Chet Ramey wrote:
>
> On 11/27/17 1:12 PM, Hans Åberg wrote:
>
On MacOS 10.13, one can set locale environment variables. The Terminal
default login shell reads .profile; xterm reads .bashrc. There are other
ways to set them system-wide, changing wit
On 11/27/17 1:12 PM, Hans Åberg wrote:
>>> On MacOS 10.13, one can set locale environment variables. The Terminal
>>> default login shell reads .profile; xterm reads .bashrc. There are other
>>> ways to set them system-wide, changing with the OS version.
>>
>> Terminal has been able to pass the
> On 27 Nov 2017, at 22:04, Chet Ramey wrote:
>
> On 11/27/17 12:51 PM, Hans Åberg wrote:
>
>> On MacOS 10.13, one can set locale environment variables. The Terminal
>> default login shell reads .profile; xterm reads .bashrc. There are other
>> ways to set them system-wide, changing with the
On 11/27/17 12:51 PM, Hans Åberg wrote:
> On MacOS 10.13, one can set locale environment variables. The Terminal
> default login shell reads .profile; xterm reads .bashrc. There are other ways
> to set them system-wide, changing with the OS version.
Terminal has been able to pass the locale env
> On 27 Nov 2017, at 19:35, Chet Ramey wrote:
>
> On 11/27/17 1:19 AM, Hans Åberg wrote:
>
The deprecated HFS uses UTF-16, but MacOS has LC_CTYPE=UTF-8; thus with no
additional qualifications like in LC_CTYPE=en_US.UTF-8. It would be
interesting to know if it is POSIX conformi
> On 27 Nov 2017, at 10:43, Stephane Chazelas
> wrote:
>
> 2017-11-26 22:40:45 +0100, Hans Åberg:
> [...]
>> The deprecated HFS uses UTF-16, but MacOS has LC_CTYPE=UTF-8;
>> thus with no additional qualifications like in
>> LC_CTYPE=en_US.UTF-8. It would be interesting to know if it is
>> POSI
On 11/27/17 1:19 AM, Hans Åberg wrote:
>>> The deprecated HFS uses UTF-16, but MacOS has LC_CTYPE=UTF-8; thus with no
>>> additional qualifications like in LC_CTYPE=en_US.UTF-8. It would be
>>> interesting to know if it is POSIX conforming, as it causes confusion with
>>> some software.
>>
>>
Joseph Myers wrote:
> On Sat, 25 Nov 2017, k...@keldix.com wrote:
>
> > systems, and also implementations that can conform using UTF-16 and
> > different 8-bit codesets. For instance 'A' is coded x0041 (two bytes) in
> > UTF-16
> > and x41 (only one byte) in cp850, and UTF-8.
>
> ISO C includes
On Sat, 25 Nov 2017, k...@keldix.com wrote:
> systems, and also implementations that can conform using UTF-16 and
> different 8-bit codesets. For instance 'A' is coded x0041 (two bytes) in
> UTF-16
> and x41 (only one byte) in cp850, and UTF-8.
ISO C includes (C99 TC2 onwards) the requirement "
2017-11-26 22:40:45 +0100, Hans Åberg:
[...]
> The deprecated HFS uses UTF-16, but MacOS has LC_CTYPE=UTF-8;
> thus with no additional qualifications like in
> LC_CTYPE=en_US.UTF-8. It would be interesting to know if it is
> POSIX conforming, as it causes confusion with some software.
Yes, I've s
> On 27 Nov 2017, at 03:16, Chet Ramey wrote:
>
> On 11/26/17 1:40 PM, Hans Åberg wrote:
>
>> The deprecated HFS uses UTF-16, but MacOS has LC_CTYPE=UTF-8; thus with no
>> additional qualifications like in LC_CTYPE=en_US.UTF-8. It would be
>> interesting to know if it is POSIX conforming, as
11 matches
Mail list logo
