The Windows OEM Codepages listed at http://www.microsoft.com/globaldev/reference/oem.mspx
are implemented as

IBM437.java
IBM737.java
IBM775.java
IBM850.java
IBM852.java
IBM855.java
IBM857.java
IBM858.java
IBM862.java
IBM866.java
IBM874.java

included in ExtendedCharsets provider, which will be pacakged into charsets.jar in the
final binary. The current deployment installation policy for JRE on Windows platform does
not install charsets.jar if it decided that the end user "might not need it" based on
certain criteria (see http://java.sun.com/j2se/1.5.0/docs/guide/intl/encoding.doc.html),
to reduce the total download size.

This does not cause big problem if java app does not use these OEM CP charsets explicitly
in the previous releases. However the newly introduced java.io.Console tries to use the Windows OEM charsets (instead of jvm's default charset) to communicate to the terminal
if the terminal is indeed using OEM codepage. The current deployment policy will force
the Console class to fallback to use the default chaset if the JRE does not have the
charsets.jar installed. So we should move these charsets into the StandardCharsets
charset provider.