{"id":34403,"date":"2005-08-29T07:00:00","date_gmt":"2005-08-29T14:00:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/oldnewthing\/2005\/08\/29\/why-is-the-default-console-codepage-called-oem\/"},"modified":"2005-08-29T07:00:00","modified_gmt":"2005-08-29T14:00:00","slug":"why-is-the-default-console-codepage-called-oem","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/oldnewthing\/20050829-00\/?p=34403","title":{"rendered":"Why is the default console codepage called &#8220;OEM&#8221;?"},"content":{"rendered":"<p><P>\nLast year, we learned that\n<A HREF=\"http:\/\/blogs.msdn.com\/oldnewthing\/archive\/2004\/05\/31\/144893.aspx\">\nthe ANSI code page isn&#8217;t actually ANSI<\/A>.\nIndeed, the OEM code page isn&#8217;t actually OEM either.\n<\/P>\n<P>\nBack in the days of MS-DOS, there was only one code page,\nnamely, the code page that was provided by the\noriginal equipment manufacturer\nin the form of glyphs embedded in the character generator\non the video card.\nWhen Windows came along,\n<A HREF=\"http:\/\/blogs.msdn.com\/oldnewthing\/archive\/2005\/03\/08\/389527.aspx\">\nthe so-called ANSI code page was introduced<\/A>\nand the name &#8220;OEM&#8221; was used to refer to the MS-DOS code page.\n<A HREF=\"http:\/\/blogs.msdn.com\/michkap\/archive\/2005\/02\/08\/369197.aspx\">\nMichael Kaplan went into more detail earlier this year\non the ANSI\/OEM split<\/A>.\n<\/P>\n<P>\nOver the years, Windows has relied less and less on the character\ngenerator embedded in the video card, to the point where the\nterm &#8220;OEM character set&#8221; no longer has anything to do with the\noriginal equipment manufacturer.\nIt is just a convenient term to refer to &#8220;the character set used\nby MS-DOS and console programs.&#8221;\nIndeed, if you take a machine running US-English Windows\n(<A HREF=\"http:\/\/www.microsoft.com\/globaldev\/reference\/oem\/437.htm\">OEM code page 437<\/A>) and install,\nsay, Japanese Windows,\nthen when you boot into Japanese Windows,\nyou&#8217;ll find that you now have\n<A HREF=\"http:\/\/www.microsoft.com\/globaldev\/reference\/dbcs\/932.htm\">\nan OEM code page of 932<\/A>.\n<\/P><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Because it once was, though no longer is.<\/p>\n","protected":false},"author":1069,"featured_media":111744,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[2],"class_list":["post-34403","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-oldnewthing","tag-history"],"acf":[],"blog_post_summary":"<p>Because it once was, though no longer is.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/34403","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/users\/1069"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/comments?post=34403"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/posts\/34403\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media\/111744"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/media?parent=34403"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/categories?post=34403"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/oldnewthing\/wp-json\/wp\/v2\/tags?post=34403"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}