From: SourceForge.net <no...@so...> - 2009-06-30 18:12:08
|
Bugs item #2814767, was opened at 2009-06-30 14:06 Message generated for change (Comment added) made by bigrixx You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2814767&group_id=119701 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: v4.0beta >Status: Closed >Resolution: Invalid Priority: 5 Private: No Submitted By: Rony G. Flatscher (orexx) Assigned to: Nobody/Anonymous (nobody) Summary: Possible codepage problem on Windows Initial Comment: The uploaded program defines a string "a" that contains German umlauts. Depending on whether one uses SAY a or 'echo "'a'"' the output is different! Stumbled over this problem analysing a problem in one of Walter Pachl's script, where he uses "dir" and "cd" via the cmd subcom, referring to directory entries that have an umlaut u (ü) as their trailing characters. The character via the cmd subcom mismatched the char extracted from a redirectred file, causing the Rexx program to fail on certain directories. The output of such strings should be the same, i.e. independent of using a Rexx SAY statement or the cmd subcom like in the given example. Using <ooRexx400_4852-x86_32-debug.exe> on a German Windows XP SP3. Default codepage in cmd.exe is therefore set to 850 (437 would be the DOS English codepage). ---------------------------------------------------------------------- >Comment By: Rick McGuire (bigrixx) Date: 2009-06-30 14:11 Message: What the commands process and how data written to the screen via various paths is out of the control of the Rexx interpreter. The data is just written to the screen using 8-bit ascii, and the OS takes it from there. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=684730&aid=2814767&group_id=119701 |