Talk:Windows code page

Way too big?
This page should link to the individual code pages instead of listing all of the tables at once (for one thing it is missing most of the mappings anyway, like for 932). --unsigned


 * ✅. Someone else apparently have already cleaned up the article.--Makkachin (talk) 00:50, 21 July 2013 (UTC)

ANSI or not?
Once and for all, is it correct to say "ANSI" to the Windows code pages? Currently, some pages on wikipedia say it's wrong (as ANSI never defined these code pages, but Microsoft just says "ANSI" to it anyway), while this article makes the impression that it is ok. --Abdull 23:53, 17 March 2006 (UTC)
 * Well microsofts technical documents use that term all over the place and i don't belive anyone uses the term ansi code page for anything else. I can't imagine ANSI are particularlly happy about having thier name put to something that isn't thiers though. I guess it all depends on how you define right and wrong ;) Plugwash 10:44, 18 March 2006 (UTC)
 * ANSI explicitly disavows any understanding of the standards they publish, and explicitly repudiates any suggestion that they have an opinion about the meaning of their standards. So if you want to say, for example, that the first 127 code points all represent the same character .... ANSI doesn't have an opinion on that. Wikipedia on the other hand....  — Preceding unsigned comment added by 124.188.134.186 (talk) 06:05, 25 October 2020 (UTC)
 * Microsoft is now leaning away from "ansi" and uses "active" instead to describe the current code page. — Preceding unsigned comment added by 131.107.0.73 (talk • contribs)

Redundant comment
"Recent Microsoft products and APIs use Unicode internally, but many applications and APIs (including Java) continue to…"
 * does the Java comment seem relevant? I mean, there are a million and one applications that use the older methods, shouldn't we name them here too ?

Removal of chart
I have removed the charts of the code pages from this article, and put all the information that was left in a miscellaneous section. I am using the latest version of the screen reader JAWS on a fairly fast computer and JAWS froze for thirty seconds when I entered this page. I almost couldn't edit the section with the chart to remove it. I can understand that happening at somewhere like articles for deletion/yesterday or requests for adminship when it is busy, but JAWS should never freeze for more than a few seconds when I enter an article. Not even the article United States is that taxing on JAWS resources. The charts for code pages are available elsewhere on the Internet in an uneditable form. Graham 87 08:29, 21 June 2007 (UTC)

Available only to managed applications?
1201 — Unicode (BMP of ISO 10646, UTF-16BE) has the following description: "Available only to managed applications" Does it make any sense to include this explanation? The 1200 - utf-16 encoding is also available only to managed applications according to the linked MS page, but here its missing. Hubalu (talk) 10:24, 30 January 2014 (UTC)

Parked stuff found on category page Category:Windows code pages
Still missing: windows-874 (redirects to ISO/IEC 8859-11), code page 50220, code page 50221, code page 50222, which are variations on ISO-2022-JP.

External links
 * Full list of Windows code pages
 * Windows Code Page reference chart
 * IANA Charset Name Registrations
 * Unicode mapping table for Windows code pages
 * Unicode mappings of windows code pages with "best fit"

windows-874:
 * Windows 874 reference chart
 * Unicode mapping table for Windows 874
 * Unicode mappings of windows 874 with "best fit"

End of stuff moved from category page.

More than two groups of code pages
There are actually 4 groups of code pages: ANSI, OEM, Mac and EBCDIC under Windows. All of them can vary dependent on the locale of the Windows version. See LOCALE_IDEFAULTMACCODEPAGE and LOCALE_IDEFAULTEBCDICCODEPAGE in this link: https://msdn.microsoft.com/de-de/library/windows/desktop/dd373761(v=vs.85).aspx

KOI8
Where is the source for “20866” designation by Microsoft? Incnis Mrsi (talk) 10:28, 3 August 2019 (UTC)