Erich, thank you very much! For readers of my original mail in this group: In [http://sourceforge.net/p/oorexx/code-0/12091] Erich added additional improvements and leaves the Unicode sequences in the text.
---rony On 15.06.2020 13:28, Rony G. Flatscher wrote: > > Looking over the changes of last night I stumbled over > <https://sourceforge.net/p/oorexx/bugs/1709/>: > > "[r12090] also changes (corrects) escape ( \ ) handling and adds support > for \u00xx escape > parsing and generation. There is still no support for general \uxxyy > parsing because we have > no Unicode support. So any JSON text with a \uxxyy sequence will now > fail (before this > change, invalid escapes, including \u escapes, would have been copied to > the output string > unmodified)". > > The change part that now raises an error if a proper JSON \uxxyy escape > sequence is encountered > means that valid JSON encodings containing Unicode escape sequences will > cause json.rex to not be > able to process them anymore as now an error gets raised. The current > incapability of ooRexx to > deal with Unicode should not cause valid JSON encodings to be regarded as an > error. It also breaks > current Rexx programs that process JSON encodings that contain such Unicode > escape sequences. > > So please just leave the unhandled Unicode escape sequence in the text and > just document this > ooRexx shortcoming in the json.rex class. > > ---rony > > P.S.: Among other things this will continue to allow BSF4ooRexx users to turn > such escape > sequences into proper Unicode renderings for interchanging with Java class > libraries. >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
