Hello Jürgen,
as far as some UTF study got me I have 2 questions:
Two bytes in range x8000 - x will be changed to x108000 - x10.
Correct?
Could it happen, that the last byte in a file is an invalid UTF-8 char -
leading to x1080__ - x10FF__. What then would be __?
Best Regard
Hi Hans-Peter,
yes, please send them.
I wonder if in your previous report "stack trace on scan each" a
workspace
was also corrupted because I am getting this:
C10←,⊂'AB12EF12IJ'
P10←(⊂2/⍳5)⊂¨C10
Hi,
I have done some rework of the UTF8-to-Unicode conversion.
It now maps incorrect characters in an UTF8 encoding to
corresponding
characters in the "Supplementary Private Use Area-B" (so that the
offending character becomes available at APL level a
Hi Jürgen,
I agree. A *cat BIN_FILE* in a terminal session is of artistically
value only.
Best Regards
Hans-Peter
Am 01.11.20 um 20:48 schrieb Dr. Jürgen Sauermann:
Hi Hans-Peter,
the result of an ⍎'ed command is the output of that command, normally
one (nested) APL string for every line o
