Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c++,comp.lang.c Subject: Re: "Unicode" Date: Mon, 05 Sep 2016 16:17:05 -0700 Organization: None to speak of Lines: 39 Message-ID: References: <57ca82af.1170031@news.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Injection-Info: mx02.eternal-september.org; posting-host="945944de09706c9b4e29b53c9d2efdc2"; logging-data="31756"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18FLa+7Bg4ajJqXnSebUQX/" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:rr153Xvpe0olq/fZbwiH4Yd0Ci8= sha1:gxDPeKSxfuIpis5+XcDOZFAUYrM= Xref: csiph.com comp.lang.c++:44888 comp.lang.c:93239 "Alf P. Steinbach" writes: > On 06.09.2016 00:35, Keith Thompson wrote: [...] >> "ANSI" is an incorrect name for the Windows-1252 8-bit character set >> (and related code pages). Even Microsoft no longer calls it that. > > “Windows ANSI” is not a name for a specific character set. > > It's the codepage specified by the ąGetACP API function, which, not very > well documented, is the codepage specified in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\CodePage> key, > item name ACP, which is short for “ANSI code page”. ACP may originally have been an abbreviation of "ANSI Code Page", and apparently it's still used as a key name for backward compatibility (which sounds reasonable). My point is that "Windows ANSI" is a misnomer. The character sets in question were intended to be an ANSI standard(s), but they were never approved. The collection of code pages sometimes referred to as "Windows ANSI" have nothing to do with the American National Standards Institute. > The information you have about deprecation of the name “ANSI” may well > be correct. Microsoft has, after all, deprecated nearly all of the > original string functions of the C library. That is, they believed they > had: but it was, just like an attempted deprecation of the name used in > their APIs, documentation, books etc., just utter nonsense. :) That's not quite the same. Microsoft's attempt to deprecate the standard string functions is absurd, since they're still in the ISO C standard. Deprecating the name "ANSI" for certain Windows-specific character sets, on the other hand, is entirely reasonable. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"