Path: ...!eternal-september.org!feeder2.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Lawrence D'Oliveiro <ldo@nz.invalid>
Newsgroups: comp.lang.fortran
Subject: Re: Upcoming gfortran 15 will contain unsigned numbers
Date: Sat, 23 Nov 2024 02:08:19 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 16
Message-ID: <vhrdej$1dqca$4@dont-email.me>
References: <veg58f$kb8e$1@dont-email.me> <vemj62$1qt5b$1@dont-email.me>
	<vemqnn$1sd2k$4@dont-email.me> <vgmj98$c89k$1@solani.org>
	<vgninl$3p2fj$1@dont-email.me> <vhrbq4$167bv$1@solani.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 23 Nov 2024 03:08:20 +0100 (CET)
Injection-Info: dont-email.me; posting-host="2fd1218dfbbc8c3afa5bbf19b4966652";
	logging-data="1501578"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/pURlJEYFv3Y2Nufk/777J"
User-Agent: Pan/0.161 (Chasiv Yar; )
Cancel-Lock: sha1:5p9pxvOPJ2NHKMqCPibh+hGxizE=
Bytes: 1819

On Fri, 22 Nov 2024 19:40:19 -0600, Lynn McGuire wrote:

> Come over here to Windows.  UTF-16 is the name of the game.  It is a
> total pain.

Microsoft (and Sun, with Java) adopted Unicode at precisely the wrong 
time, back when everybody believed the Unicode folks who said that it 
would remain a fixed-length 16-bit code.

> Microsoft is rumored to be working on a UTF-8 API for Win32 / Win64.  I
> will believe it when I see it.

Linux simply ignored the issue. Filespecs passed to the kernel are split 
at ASCII “/” characters and terminated by NUL. And those are the only byte 
values with special interpretations; file/directory names are free to 
contain anything else. As a result, it works seamlessly with UTF-8.