In <[EMAIL PROTECTED]>, on 10/03/2005
at 12:35 PM, Paul Gilmartin <[EMAIL PROTECTED]> said:
>It's the 0xAC. I know you periodically chastise persons who submit
>non-USASCII text and fail to indicate the code page. This ought to
>apply even more to persons who post code in ASCII extensions intended
>to run on an EBCDIC system and fail to indicate both the ASCII and
>EBCDIC pages needed for translation.
I agree with half of that; it should apply to persons who post
non-ASCII code without indicating the character set. I don't believe
that the author should be responsible for the PC-EBCDIC translation.
Does anyone know what the proper code pages are to request iconv to
convert an ISO-8859-1 ¬ (AC) to an EBCDIC ¬?
>And, in one of the files, I see:
>grep '[\\/¬] *='
> /* IF LINE = JLIN & TY_FL /= 'Y' THEN CALL TYPRUN */
Is that even legal REXX?
>(I hadn't realized "/=" is an acceptable form;
AFAIK it isn't. Of course, even if it is valid you are correct that
mixing forms makes the code harder to read.
>And, for the individual who sent me privately the two files as
>attachments, still containing the non-USASCII character,
>('Content-Type: text/plain; charset="iso-8859-1"'), but still with
>no indication of the EBCDIC code page to use:
That's sounds like he did what he was supposed to do, assuming that he
also had the accompanying header fields, e.g.,
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
