IsValidCodePage
Functional Difference from WIN95
N/A
Functional Difference from SBCS Open32
New
Implementation
This API determines whether a specified code page is valid or not. A code page is considered valid if it is installed in the system like as WIN95. As for the code-page identifier, see 'Comparison table of code pages'. The list of the valid codepages are initialized by Open32 constructor useNLS when the process begins. Open32 gets the codepages by WinQueryCpList. Among them, Open32 determines them as valid, when they are listed in the Open32 hard-coded list of ANSI codepages and OEM codepages. In fact, Open32 should, furthermore, confirm that ULS codepage object for these codepages are available. ULS codepage object is the file; IBMxxx (xxx is the codepage ID) at the "ULSPATH"/codepage. "ULSPATH" is the environment variable. But this confirmation is not always true because there's a case whose ULS codepage object is an alias to another ULS codepage object. In this case, what we can do is only to try to create the UCONV object, but it takes time to load a large codepage object. That's why this confirmation is skipped.