Kbase P133198: Single byte code page and ICU collation does not raise error 1043
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/17/2008 |
|
Status: Unverified
SYMPTOM(s):
Single byte code page and ICU collation does not raise error 1043
Starting a session using a single byte -cpinternal code page value and an ICU collation setting, does not display error 1043.
Collation table for code page <code-page> and collation name <collation-name> was not found in <filename>. (1043)
Starting a session with:
prowin32.exe -cpinternal 1252 -cpstream 1252 -cpcoll ICU-fr
Should display error 1043, since the collation ICU-fr is not a collation of the 1252 code page. But it doesn't and the session starts as normal.
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
CAUSE:
This is expected behavior. Beginning with OpenEdge 10.0B04 Progress converts all characters from -cpinternal to Unicode for collation. Since ICU collations work with Unicode, ICU collations can handle any -cpinternal setting. So there is no such thing as an 'invalid code page' for any ICU collation. This is why ICU collations are allowed for single byte code pages.
FIX:
When starting a session, use either a defined collation for a specific code page page, or use a corresponding code page from the ICU.