In article <[email protected]> you wrote:
> (Cross posting to ISPF-L and IBM-MAIN)
> On 2014-01-10, at 12:59, Don Poitras wrote:
> >
> >>> As of z/OS 2.1, ISPF supports UTF-8, so a binary transfer will still show
> >>> an A if it
> >>> was an A on the PC. ...
> >> What representation does it use in the 3270 data streams? Is
> >> this well documented in the Data Streams reference? What must
> >> it do to avoid embedded 3270 command bytes? Is this compatible
> >> with Yale/7271/IND$FILE/Kermit conventions?
> >
> > As far as 3270 goes, I think it's just going to us the CODEPAGE
> > and CHARSET you start ISPF with. I think it's going to be limited
> > to the set of EBCDIC code pages. As this is the first release, I'm
> > sure there's stuff missing that will be added as time goes by.
> >
> I guess that conforms to someone's notion of "support". Should
> I understand that one can edit UTF-8 files; one just can't see
> most of the characters. I guess any meaningful editing must be
> done with macros.
> (I don't yet have access to 2.1.) What happens if I turn HEX ON?
> Will it show the value of the Unicode code point, or of the
> UTF-8 sequence of bytes. Generally, neither can be represented
> in two hex digits.
I don't know how these characters are going to survive email, so
I'll describe what I did. Just editing all the hex from 00 to FF
in EBCDIC mode, you end up with lots of glyphs that are two-byte
in UTF-8. I copied one line using my emulator cut and paste and
pasted the glyphs in a new member that I specified to be created
using UTF-8. I then used the text split line command to put the
first 5 glyphs each on a single line. The glyphs are:
1. logical not
2. pound (english money not weight)
3. Yen
4. Middle dot
5. Copyright
I had to position the cursor on the correct hex byte to properly
do the text-split. It's real easy to mess up the file.
EDIT SASDTP.ISPF.CNTL(UTF8) - 01.02
Command ===>
****** ***************************** Top of Data
000001 ??????????????????????????]????
CACACACBCACACBCBCBCBC9CACA5CBC922222222222
2C2325272927262C2D2E3D282FD243700000000000
-------------------------------------------------
000002 ??
CA2222222222222222222222222222222222222222
2C0000000000000000000000000000000000000000
-------------------------------------------------
000003 ??
CA2222222222222222222222222222222222222222
230000000000000000000000000000000000000000
-------------------------------------------------
000004 ??
CA2222222222222222222222222222222222222222
250000000000000000000000000000000000000000
-------------------------------------------------
000005 ??
CB2222222222222222222222222222222222222222
270000000000000000000000000000000000000000
-------------------------------------------------
000006 ??
CA2222222222222222222222222222222222222222
290000000000000000000000000000000000000000
> On 2014-01-10, at 16:19, Steve Comstock wrote:
> >>
> >> BTW, how can I convert majuscule->minuscule with ISPF EDIT.
> >> I know; I could write a macro ... Sheesh!
> >
> > Well, on a command line:
> > c p'>' p'<' all
> >
> > Or, as a line command:
> > LCC
> > ...
> > LCC
> > should do it.
> >
> Thanks. I hadn't known about that. So if my UTF-8 file I have:
> ==> Polyglot <==
> A common Russian phrase is "????? ??????".
> The Greek might be "???? ????."
> ... will those commands transform it to:
> ==> polyglot <==
> a common russian phrase is "????? ??????".
> the greek might be "???? ????."
> ... even as Vim and LibreOffice do, and even if I can't see it?
> -- gil
--
Don Poitras - SAS Development - SAS Institute Inc. - SAS Campus Drive
[email protected] (919) 531-5637 Cary, NC 27513
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
