Kbase P117244: What code page should be used for Progress Character Client sessions on Windows?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
01/07/2009 |
|
Status: Unverified
GOAL:
Can I use -cpstream iso8859-1 for a Progress Character Session running on MS-DOS?
GOAL:
Which codepage should I use for -cpstream for a character session running on MS-DOS?
GOAL:
Can the Windows -cpinternal and -cpstream setting be used for Character Client sessions?
GOAL:
What code page should be used for Progress Character Client sessions?
FACT(s) (Environment):
Windows
Progress 8.x
Progress 9.x
OpenEdge 10.x
FIX:
MS-DOS uses a different character set than both UNIX and Windows (GUI) operating systems. In a Windows client there are two codepages in operation, one for the DOS system and another for Windows. The DOS command prompt and typically Character-based applications use the DOS code page, while Windows GUI-based applications use the Windows code page. For example a Western Windows GUI client should use the Microsoft code page 1252, and the DOS code page should be ibm850 or ibm437.
So iso8859-1 (and other ISO code pages) and 1252 (and other Windows GUI code pages) should not be used with Progress Character Client sessions on Windows. The code page that should be used for these sessions depends on the DOS OEM code page being used on that specific machine. To verify the DOS "Active" code page being used, start a DOS command prompt and type "CHCP". For example, if this returns 850, then this is ibm850.
On Progress Character client sessions -cpinternal should be set to the code page being used by the OEM DOS system. In addition to this -cpstream should probably also be set to the DOS OEM code page. This is because in Character sessions (like GUI sessions), -cpstream dictates the code page used for streaming input and output, as well as printing. But unlike GUI sessions the -cpstream code page also dictates the code page used for keyboard entry and screen display.