Re: Character encoding conversion in wide string literals

Path	csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From	Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups	comp.lang.c++
Subject	Re: Character encoding conversion in wide string literals
Date	Tue, 07 Dec 2021 12:26:38 -0800
Organization	None to speak of
Lines	46
Message-ID	<87ilw0b1q9.fsf@nosuchdomain.example.com> (permalink)
References	<sonh15$g9j$1@gioia.aioe.org> <sonvh8$vc9$1@dont-email.me> <87r1aob9d3.fsf@nosuchdomain.example.com> <soo9cs$9th$1@dont-email.me>
Mime-Version	1.0
Content-Type	text/plain
Injection-Info	reader02.eternal-september.org; posting-host="7f90512ec77176d2b122f800cb8bb3bb"; logging-data="17099"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18JGUrCNEyzuPoLEx3t5kGx"
User-Agent	Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Cancel-Lock	sha1:zveK5AUyB9zLzHQhvAILu7d+mmg= sha1:zU4ftUEZsEfO7g+IuMuaMGEuWnY=
Xref	csiph.com comp.lang.c++:82582

Show key headers only | View raw

Paavo Helde <eesnimi@osa.pri.ee> writes:
> 07.12.2021 19:41 Keith Thompson kirjutas:
>> What exactly do you mean by "Windows ANSI"?  Windows-1252 or
>> something
>> else?  (Microsoft doesn't call it "ANSI", because it isn't.)
>
> It does. From
> https://docs.microsoft.com/en-us/windows/win32/api/winnls/nf-winnls-getacp
>
> "Retrieves the current Windows ANSI code page identifier for the
> operating system."

Yes, I has missed that.

But Microsoft has also said:

    The term ANSI as used to signify Windows code pages is a historical
    reference, but is nowadays a misnomer that continues to persist in
    the Windows community.

https://en.wikipedia.org/wiki/Windows-1252
https://web.archive.org/web/20150204175931/http://download.microsoft.com/download/5/6/8/56803da0-e4a0-4796-a62c-ca920b73bb17/21-Unicode_WinXP.pdf

Microsoft's mistake was to start using the term "ANSI" before it
actually became an ANSI standard.  Once that mistake was in place,
cleaning it up was very difficult.

> This is in contrast to the GetOEMCP() function which is said to return
> "OEM code page", not "ANSI code page". Both terms are misnomers from
> the previous century.
>
> Both these codepage settings traditionally refer to some narrow char
> codepage identifiers, which will vary depending on the user regional 
> settings and are thus unpredictable and unusable for basically
> anything related to internationalization.
>
> The only meaningful strategy is to set these both to UTF-8 which now
> finally has some (beta stage?) support in Windows 10, and to upgrade
> all affected software to properly support this setting.

Yes, I advocate using UTF-8 whenever practical.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips
void Void(void) { Void(); } /* The recursive call of the void */

Thread

Character encoding conversion in wide string literals Juha Nieminen <nospam@thanks.invalid> - 2021-12-07 11:37 +0000
  Re: Character encoding conversion in wide string literals "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2021-12-07 16:44 +0100
    Re: Character encoding conversion in wide string literals James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-12-07 11:48 -0500
      Re: Character encoding conversion in wide string literals "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2021-12-07 18:59 +0100
        Re: Character encoding conversion in wide string literals James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-12-07 13:55 -0500
        Re: Character encoding conversion in wide string literals Öö Tiib <ootiib@hot.ee> - 2021-12-07 16:39 -0800
        Re: Character encoding conversion in wide string literals David Brown <david.brown@hesbynett.no> - 2021-12-08 09:18 +0100
    Re: Character encoding conversion in wide string literals Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-12-07 09:41 -0800
      Re: Character encoding conversion in wide string literals "Alf P. Steinbach" <alf.p.steinbach@gmail.com> - 2021-12-07 19:07 +0100
        Re: Character encoding conversion in wide string literals Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-12-07 12:21 -0800
      Re: Character encoding conversion in wide string literals Paavo Helde <eesnimi@osa.pri.ee> - 2021-12-07 20:32 +0200
        Re: Character encoding conversion in wide string literals James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-12-07 13:55 -0500
        Re: Character encoding conversion in wide string literals Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2021-12-07 12:26 -0800
  Re: Character encoding conversion in wide string literals James Kuyper <jameskuyper@alumni.caltech.edu> - 2021-12-07 11:38 -0500
    Re: Character encoding conversion in wide string literals Manfred <noname@add.invalid> - 2021-12-07 19:07 +0100

csiph-web