From owner-freebsd-questions@freebsd.org Thu Jun 11 22:42:15 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5D9103442BC for ; Thu, 11 Jun 2020 22:42:15 +0000 (UTC) (envelope-from kh@panix.com) Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49jf4Q5D79z4Wnh for ; Thu, 11 Jun 2020 22:42:14 +0000 (UTC) (envelope-from kh@panix.com) Received: from rain.home (pool-173-48-64-3.bstnma.fios.verizon.net [173.48.64.3]) by mailbackend.panix.com (Postfix) with ESMTPSA id 49jf4Q14BFzqnK for ; Thu, 11 Jun 2020 18:42:14 -0400 (EDT) Subject: Re: freebsd vs. netbsd To: freebsd-questions@freebsd.org References: <171506d5-19aa-359e-c21d-f07257c52ebd@freenetMail.de> <62d10000-e068-922e-23bd-f7a61e7a4e89@anatoli.ws> <6a4f6a15-ec43-03f6-1a41-a109e445f026@anatoli.ws> <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> <20200610063555.00003707@seibercom.net> <82F57D0D-E0EC-49F7-824E-20A296C9F549@kicp.uchicago.edu> <250b853a-b436-0e99-b05c-9abd6b6019ef@panix.com> <20200611070630.2cb42786.freebsd@edvax.de> <20200611075658.1dd841a9.freebsd@edvax.de> <20200611082443.0000187a@seibercom.net> <2e6c6baf-9d87-2a02-00c3-578c6630f97f@kicp.uchicago.edu> <20200611172537.2f7cdc07@archlinux> From: Kurt Hackenberg Message-ID: Date: Thu, 11 Jun 2020 18:42:11 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <20200611172537.2f7cdc07@archlinux> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49jf4Q5D79z4Wnh X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of kh@panix.com designates 166.84.1.89 as permitted sender) smtp.mailfrom=kh@panix.com X-Spamd-Result: default: False [-1.79 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RWL_MAILSPIKE_GOOD(0.00)[166.84.1.89:from]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:166.84.0.0/16]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.98)[-0.980]; DMARC_NA(0.00)[panix.com]; NEURAL_SPAM_SHORT(0.26)[0.258]; RCVD_IN_DNSWL_MED(-0.20)[166.84.1.89:from]; NEURAL_HAM_MEDIUM(-0.56)[-0.565]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:2033, ipnet:166.84.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[]; RECEIVED_SPAMHAUS_PBL(0.00)[173.48.64.3:received] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Jun 2020 22:42:15 -0000 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? :-)