UTF-8 is a transform of Unicode that has been endorsed by the IETF; see RFC 5198. Over time, support will become increasingly critical.
Do not see RFC 4042. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Joel C. Ewing [jce.ebe...@cox.net] Sent: Sunday, May 16, 2021 10:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: XMITIP - NLS support for Arabic character Terminology Clarification: UTF-8 is of course just one representation of the Unicode codeset, not the codeset itself. UTF-8 has the advantage that characters in standard ASCII charset have identical byte representation in UTF-8, which makes possible some use of UTF-8 even in email headers. I don't know whether CSSMTP employs EBCDIC to ASCII conversion for everything or has the smarts to restrict that conversion to headers and ordinary text. If for everything, then obviously the only way to send UTF-8 via XMITIP, JES and CSSMTP would be for XMITIP to put it in the email body as a base-64 encoded segment. The most complete solution for full-function email from z/OS a decade ago was to pass the email directly to an SMTP server on a Unix or Windows platform. That may still be true. JC Ewing On 5/16/21 8:11 AM, Joel C. Ewing wrote: > I think there is a misconception here about codesets. iconv converts > characters in one codeset to corresponding characters in another codeset > , PROVIDED the character exists in the other codeset. The character > codes supported in the target codeset are by definition fixed. If > there is no corresponding character code in the target codeset, you > would expect the original character to vanish. > > What is needed is some way for XMITIP to support using Unicode UTF-8 in > an email within the constraints of the EBCDIC character codeset expected > by JES and by the parameters to XMITIP. You could then in theory send > email containing any national EBCDIC codeset by using iconv to convert > any special language codeset to UTF-8 and send it as UTF-8 characters > > It should at least be possible to tell XMITIP to use a file in UTF-8 > codeset for the email body and have XMITIP use base-64 encoding for the > email body like was forced in past years (and even occasionally today) > by some email transfer agents that don't advertise support for 8-bit > characters. Perhaps there is not even a serious conflict with just > telling XMITIP that its email data is to be handled as UTF-8 and having > XMITIP put it in in the JES queue as UTF-8 with appropriate header > information, assuming that such can be handled by the z/OS email address > space without problems. > > Support for generating an email with content that is UTF-8 could > certainly be added to XMITIP in some form. Formatting the email > manually with the required control information is certainly another > possibility, but would be a pain to be avoided. > Joel C Ewing > > On 5/16/21 2:22 AM, Peter wrote: >> Hello >> >> I did but file.txt is empty, but the command executed successfully >> >> On Sun, 16 May, 2021, 11:01 am Mike Schwab, <mike.a.sch...@gmail.com> wrote: >> >>> The Greater than symbol sends the output to the file. >>> Try again without the Greater than symbol so it is the output file. >>> >>> On Sun, May 16, 2021 at 1:36 AM Peter <dbajava...@gmail.com> wrote: >>>> Hello Paul >>>> >>>> I used this command from OMVS >>>> >>>> iconv -f IBM-420 -t IBM-1047 file.txt>file.txt.converted >>>> >>>> I see the converted file is empty, Should I have file.txt populated with >>>> ARABIC codes in it ? >>>> >>>> Peter >>>> >>>> On Tue, 11 May, 2021, 8:02 pm Paul Gilmartin, < >>>> 0000000433f07816-dmarc-requ...@listserv.ua.edu> wrote: >>>> >>>>> On Tue, 11 May 2021 10:21:28 +0400, Peter wrote: >>>>> >>>>>> Hi >>>>>> >>>>>> I understand CSSMTPA Doesnt support IBM-420 , but I guess ICONV >>> services > ... > -- Joel C. Ewing ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
