> I consider RFC 3676 an abomination, totally unsuitable for posting code > samples.
Why? Do you know of any case where a properly behaving mail client mangles code properly formatted with format=flowed? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Paul Gilmartin <[email protected]> Sent: Saturday, June 30, 2018 8:53 PM To: [email protected] Subject: Formatting (was: JCL ERROR : IGD01022I) On 2018-06-29, at 13:19:38, Ed Jaffe wrote: > On 6/29/2018 9:00 AM, Lizette Koehler wrote: >> I cannot read the JCL listing. Please put at least 3 spaces when pasting >> JCL into email >> >> For example without spaces > [snip] > > The formatting problem is not due to a lack of leading spaces. The problem is > trailing whitespace. With all trailing spaces removed, JCL should render AOK. > In fact, Lizette may have a valid point, without stating a reason, which may lie in or around: https://secure-web.cisco.com/1IEKxYymw-faaABElSPcn7NMPT5uaebGx6eDwIDXu5PsVp6jf2POQOLccU0stXmIrC_e5QXhmf2bTFd5cfWOT3Q5Vy5k6A8YGX7iRpTUtMCr5jdc6kdHbdr9-qLTEGpukPPQdGCJH_o2_OA9KHSWkGyOrkaHvj2VfnpqC_DN4Stbjr5l-_kGj9uO77r1QcpqTeLWn7Lyk5EqBcuHkJh1lIyfA4z-cAy6bl6YbPfevsb09_Dsi6bKFzoe7xxFJBs7Q220aPnS1Ejv8_PauSeHZ1F4ypLo5wrbTgEmUfNsUv1Srf6K9OTG9orO6-3D6Tc03-8VrsRllyRfDIdYJw5TqhIJxbbGQAi8beDlVAK1PCrUEDR3KTMiXyYZNniyLS_i6aTbuMDKI_zARSBwxjrIq5jWxL5FEQI9EL4qBWJGoKyK8fvM2-IVYG-AgJxoannP9/https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc3676#section-4.1 However, the OP had merely: Content-Type: text/plain; charset=UTF-8 ... not "Format=Flowed", so RFC 3676 does not apply. I consider RFC 3676 an abomination, totally unsuitable for posting code samples. A MUA should provide an option to override it. As an experiment, I'll append 3 copies of a text/plain file with different Content-Transfer-Encoding: 8bit, quoted-printable, and base64, inline, but no Format=Flowed. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN Кириллица (just to force Unicode.) ....+....|....+....|....+....|....+....|....+....|....+....|....+....|....+....| Trailing blanks to column 50: //* 80 columns //* 80 columns again Long line after empty line: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN Кириллица (just to force Unicode.) ....+....|....+....|....+....|....+....|....+....|....+....|....+....|....+....| Trailing blanks to column 50: //* 80 columns //* 80 columns again Long line after empty line: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN Кириллица (just to force Unicode.) ....+....|....+....|....+....|....+....|....+....|....+....|....+....|....+....| Trailing blanks to column 50: //* 80 columns //* 80 columns again Long line after empty line: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ---------------------------------------------------------------------- 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
