ooRexx under Windows run in codepage IBM850 (DOS) that cause problems as one use it on systems that use national characters beyond a-z.
National characters under IBM850 have another position than under codepage Win1252 that the ui run under, so one has to compensate for that to use rexxutil functions, ole, sqlite, jdbc etc. and on top of that the GUI script editor one use has to support codepage IBM850 to be useful. Yes, one can use an editor for DOS window as well, but ...
I found rexx code that can translate to UTF-8 and then between a number of codepages, but would rather skip it if there where a solid solution.
When I issue the chcp command from a command prompt on my Windows 10 system I get 437, not 850. Why do you think "ooRexx under Windows run in codepage IBM850 (DOS) "?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
oorexx doesn't really run with any codepage. The language definition just
uses the byte codes from '00'x to 'ff'x asis. The code points that any
meaning to the language happen to be invariant across the code pages. The
one exception is the mainframe logical not character, which oorexx declares
as being 'aa'x.
Code pages only become an issue when passing data to the OS, which
interprets the strings using its own conventions. There things get a little
dicey.
When I issue the chcp command from a command prompt on my Windows 10
system I get 437, not 850. Why do you think "ooRexx under Windows run in
codepage IBM850 (DOS) "?
Dicey is the word here... as one has to translate everything back and forth all the time for various calls. What problems may arise to make ooRexx use the codepage the ui run with?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ooRexx under Windows run in codepage IBM850 (DOS) that cause problems as one use it on systems that use national characters beyond a-z.
National characters under IBM850 have another position than under codepage Win1252 that the ui run under, so one has to compensate for that to use rexxutil functions, ole, sqlite, jdbc etc. and on top of that the GUI script editor one use has to support codepage IBM850 to be useful. Yes, one can use an editor for DOS window as well, but ...
I found rexx code that can translate to UTF-8 and then between a number of codepages, but would rather skip it if there where a solid solution.
Any ideas how to address the issue?
When I issue the chcp command from a command prompt on my Windows 10 system I get 437, not 850. Why do you think "ooRexx under Windows run in codepage IBM850 (DOS) "?
oorexx doesn't really run with any codepage. The language definition just
uses the byte codes from '00'x to 'ff'x asis. The code points that any
meaning to the language happen to be invariant across the code pages. The
one exception is the mainframe logical not character, which oorexx declares
as being 'aa'x.
Code pages only become an issue when passing data to the OS, which
interprets the strings using its own conventions. There things get a little
dicey.
Rick
On Tue, Jul 14, 2020 at 1:16 PM Gil Barmwater orange-e@users.sourceforge.net wrote:
Dicey is the word here... as one has to translate everything back and forth all the time for various calls. What problems may arise to make ooRexx use the codepage the ui run with?
The Nordic countries use it, the same in newer versions of Windows as well.