I'm using office365 and lookout from a web browser, and I don't know what they're doing. Given that it's m$, they're probably not doing what they should be. Still, I wouldn't expect even m to capriciously insert NBSP, although their it smarts quotes are almost as bad.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Paul Gilmartin <0000000433f07816-dmarc-requ...@listserv.ua.edu> Sent: Monday, December 10, 2018 6:36 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Breaking text file at position 72? On 2018-12-10, at 15:44:31, Charles Mills wrote: > It has nothing to do with MS-Word but yes, MS-Word also follows this > convention. No, the lines are nowhere near of equal length. Fold would > probably work. I have z/OS of course. But as I said I now have the problem > solved. Several good solutions presented here. It's a totally reasonable > "non-mainframey" text file. It has no carriage returns except at logical > points, not at an arbitrary line width point. Most e-mails you get follow > this convention (other than old listserves that break up lines like this one). > Does it? I hadn't noticed. And automatic text flowing/paragraphing can be infuriating when someone posts a code sample as earlier today. In fact in that sample, alternate blanks appeared as NBSP. And Shmuel (sometimes; not always) manages to send posts that don't soft wrap when I resize the window. Perhaps he uses NBSP rather than SP. -- gil ---------------------------------------------------------------------- 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
