Expected names of Microsoft Windows "ANSI" Code Pages (Encodings)
I was asked about our use of the windows "ansi" code page names, as used in things like MIME types, http content-type tags, etc. Each "code page" has a name that most accuratly round trips back to the same code page, which I've listed as the "preferred name" below. Additionally, when you ask for a code page matching a name, some code pages have several aliases that map to the identical behavior. (listed as "aliases" in the table below).
Note that there are quite a few inconsistencies and other odd behaviors. Some have names of windows-xxx, and others don't even recognize that form as an alias. Additionally some reference material I've seen refers to any microsoft code page in the windows-xxxx or CPxxx form, whether or not windows itself recognizes those names.
We have no intention of trying to create a more consistent naming scheme, we prefer that applications use Unicode.
So in practice, you should use the "preferred name" to identify data tagged by a particular code page, but if you are accepting input data, recognize that it may also use one of the listed aliases. Encoding.GetEncoding() should "do the right thing". You might want to look at my previous posts "Encoding.GetEncodings() has a couple "duplicate" names" and "What's my Encoding Called?".
Code Page 874 (ANSI/OEM - Thai)
Code Page 932 (ANSI/OEM - Japanese Shift-JIS)
Code Page 936 (ANSI/OEM - Simplified Chinese GBK)
Code Page 949 (ANSI/OEM - Korean)
Code Page 950 (ANSI/OEM - Traditional Chinese Big5)
Code Page 1250 (ANSI - Central Europe)
Code Page 1251 (ANSI - Cyrillic)
Code Page 1252 (ANSI - Latin I)
Code Page 1253 (ANSI - Greek)
Code Page 1254 (ANSI - Turkish)
Code Page 1255 (ANSI - Hebrew)
Code Page 1256 (ANSI - Arabic)
Code Page 1257 (ANSI - Baltic)
Code Page 1258 (ANSI/OEM - Viet Nam)