(Subject: changed again. Lotsa trimming for relevance.) On Mon, 10 Jul 2023 09:15:00 +0000, Seymour J Metz wrote:
>I believe that you're thinking of the WorkStation Agent, which, alas, IBM has >dropped. I found it extremely useful, despite the awful limitations of >cut-and-paste. > >What I really want is X11 support in TSO and ISPF. > Wouldn't an alternative be extending the 3270 data stream definition to support Unicode? As Attila has averred, ISPF has proven flexible in adapting to data formats and terminal capabilities. I'd expect terminal emulators that welcomed the enhancement. And bidi so users wouldn't need to type backwards. Or does CP424 already DTRT? >________________________________________ >From: Joel C. Ewing >Sent: Saturday, July 8, 2023 11:17 AM > >To call this "handling UTF-8 data" is being overly generous. If the >UTF-8 data contains more unique characters that can fit within the >limited number of characters of any 3270 terminal codeset, then you are >obviously SOL, in that you couldn't even invent a new terminal codeset >that could be used as a translation target without loss of information. >When you actually need to represent an expanded number of unique >characters, there is no way to just "convert" UTF-8 to and from any 3270 >terminal CCSID and get a meaningful result. >On 7/7/23 21:01, Attila Fogarasi wrote: >> ISPF was enhanced years ago to handle both ASCII and UTF-8 data. The EU >> command edits the file containing UTF-8 data and converts it to the CCSID >> of your terminal. If the file is tagged with CCSID 1208 then the E command >> automatically does this UTF-8 to terminal codepage conversion. It's up to >> you to be using an appropriate terminal codepage for the data you are >> editing :) -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
