Date: Thu, 11 Jun 2020 18:42:11 -0400 From: Kurt Hackenberg <kh@panix.com> To: freebsd-questions@freebsd.org Subject: Re: freebsd vs. netbsd Message-ID: <b1d78ca6-f5f8-02d0-25c6-b53d21771fd6@panix.com> In-Reply-To: <20200611172537.2f7cdc07@archlinux> References: <171506d5-19aa-359e-c21d-f07257c52ebd@freenetMail.de> <62d10000-e068-922e-23bd-f7a61e7a4e89@anatoli.ws> <ACE27C81-9437-41D6-BBD4-FA7A7B791428@kicp.uchicago.edu> <6a4f6a15-ec43-03f6-1a41-a109e445f026@anatoli.ws> <f667e8f9-b279-a3ce-3fc4-224ba17f4bbb@kicp.uchicago.edu> <00225a04-237d-9051-9aea-12c192106a20@anatoli.ws> <373EDB20-C750-42E2-A41B-EA61F6E49807@kicp.uchicago.edu> <20200609120136.00005b3c@seibercom.net> <2393a1e0-b073-950a-78be-9f57d8e9934b@anatoli.ws> <e1f6623a-3b3c-a43e-446a-d41f20f69418@kicp.uchicago.edu> <20200610063555.00003707@seibercom.net> <82F57D0D-E0EC-49F7-824E-20A296C9F549@kicp.uchicago.edu> <250b853a-b436-0e99-b05c-9abd6b6019ef@panix.com> <20200611070630.2cb42786.freebsd@edvax.de> <EA869B95-9D98-4ECC-9371-C57A0035BC32@kreme.com> <20200611075658.1dd841a9.freebsd@edvax.de> <20200611082443.0000187a@seibercom.net> <2e6c6baf-9d87-2a02-00c3-578c6630f97f@kicp.uchicago.edu> <20200611172537.2f7cdc07@archlinux>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2020-06-11 11:25, Ralf Mardorf via freebsd-questions wrote: > There's still the issue with line wrapping. Due to the small screens of > mobile phones and unwillingness to change the orientation of the > phones, we suffer from the dispute of wrapping lines at around 70 or 80 > chars vs endless lines. Small screens, small windows on big screens, windows much wider than 80 characters, variable-size windows. That's a real problem, and solved cleanly, for text in some human languages, by software that automatically fills and word-wraps text to use whatever width is available. But it's often done by redefining the ASCII characters carriage return and line feed. Originally they meant, respectively, move the print head to the left margin, and roll the paper up a line. Fill-and-wrap software often redefines the two-character sequence CRLF to mean end of paragraph. And, of course, nothing in the text tells other software that those characters have been redefined. There are solutions for email that don't involve trying to twist a character set: text/plain format=flowed (RFC 3676), text/enriched, and an unofficial trick with quoted-printable that I've seen used by AppleMail. All we have to do is persuade mail readers to implement them, and people to use them. Easy, right? :-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b1d78ca6-f5f8-02d0-25c6-b53d21771fd6>