Samuel Johnson was a misogynist. Asfor ISPF, the solution, IMHO, for IBM to open source the WSA and for someone to port it to, e.g., Linux. Getting ISPF to handle UTF-8 in the session would be gravy.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Tuesday, August 7, 2018 4:15 PM To: [email protected] Subject: EBCDIC (was: Json table characters) On Tue, 7 Aug 2018 14:48:30 +0000, Seymour J Metz wrote: >>Don't we celebrate diversity. > >In cusine, il va sans dire. In character sets, not so much. With the advent of >Unicode and UTF-8, I wish those other code pages would go away. Or at least >that every OS tagged character files with the code page and did the >translations. > And that Classic data sets could be so tagged. Also JES spool files. There is a CCSID keyword on DD statements, but severely restricted. ISPF Edit has a surprising (cf. Samuel Johnson's dog) facility for recognizing tags and dealing with many code pages, even UTF-8, *provided* their characters are supported by the terminal's character set. I wish that TSO/ISPF supported UTF-8 terminal emulators. If there were UTF-8 terminal emulators. What's the history of IBM-1047? Why does it seem to be controversial? Does it have the same set of printable glyphs as IBM-037 or IBM-500? What need impelled it? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
