From nobody Thu Jun 23 06:33:04 2022 X-Original-To: freebsd-doc@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 03C1C86C923; Thu, 23 Jun 2022 06:33:15 +0000 (UTC) (envelope-from grog@lemis.com) Received: from smtp03.aussiebb.com.au (smtp03.aussiebb.com.au [121.200.0.94]) (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 4LT9Rt0ZRzz4Yk6; Thu, 23 Jun 2022 06:33:13 +0000 (UTC) (envelope-from grog@lemis.com) Received: from localhost (localhost [127.0.0.1]) by smtp03.aussiebb.com.au (Postfix) with ESMTP id B74661A0015; Thu, 23 Jun 2022 16:33:07 +1000 (AEST) X-Virus-Scanned: Debian amavisd-new at smtp03.aussiebb.com.au Received: from smtp03.aussiebb.com.au ([127.0.0.1]) by localhost (smtp03.aussiebb.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cQTNrwBcGz8N; Thu, 23 Jun 2022 16:33:07 +1000 (AEST) Received: by smtp03.aussiebb.com.au (Postfix, from userid 119) id A7F251A0010; Thu, 23 Jun 2022 16:33:07 +1000 (AEST) X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on smtp03.aussiebb.com.au X-Spam-Level: * X-Spam-Status: No, score=1.4 required=10.0 tests=KHOP_HELO_FCRDNS,RDNS_DYNAMIC, SPF_HELO_NONE autolearn=disabled version=3.4.4 Received: from eureka.lemis.com (121-200-11-253.79c80b.mel.nbn.aussiebb.net [121.200.11.253]) by smtp03.aussiebb.com.au (Postfix) with ESMTP id 5B8CD1A0003; Thu, 23 Jun 2022 16:33:05 +1000 (AEST) Received: by eureka.lemis.com (Postfix, from userid 1004) id F21082635BD; Thu, 23 Jun 2022 16:33:04 +1000 (AEST) Date: Thu, 23 Jun 2022 16:33:04 +1000 From: Greg 'groggy' Lehey To: Polytropon Cc: grarpamp , freebsd-doc@FreeBSD.org, postmaster@FreeBSD.org, freebsd-current@FreeBSD.org, freebsd-questions@FreeBSD.org Subject: Re: Posting Netiquette [ref: Threads "look definitely like" unreadable mess. Handbook project.] Message-ID: <20220623063304.GB59423@eureka.lemis.com> References: <20220623030118.GA59423@eureka.lemis.com> <20220623060320.aad6a631.freebsd@edvax.de> List-Id: Documentation project List-Archive: https://lists.freebsd.org/archives/freebsd-doc List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-doc@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="K8nIJk4ghYZn606h" Content-Disposition: inline In-Reply-To: <20220623060320.aad6a631.freebsd@edvax.de> Organization: The FreeBSD Project Phone: +61-3-5309-0418 Mobile: +61-490-494-038. Use only as instructed. WWW-Home-Page: https://www.FreeBSD X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 User-Agent: Mutt/1.6.1 (2016-04-27) X-Rspamd-Queue-Id: 4LT9Rt0ZRzz4Yk6 X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of grog@lemis.com has no SPF policy when checking 121.200.0.94) smtp.mailfrom=grog@lemis.com X-Spamd-Result: default: False [0.89 / 15.00]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; FREEFALL_USER(0.00)[grog]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; DMARC_NA(0.00)[FreeBSD.org]; AUTH_NA(1.00)[]; R_SPF_NA(0.00)[no SPF record]; RCPT_COUNT_FIVE(0.00)[6]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_MEDIUM(1.00)[0.999]; NEURAL_SPAM_LONG(1.00)[0.999]; NEURAL_HAM_SHORT(-0.21)[-0.212]; MLMMJ_DEST(0.00)[freebsd-current,freebsd-doc,freebsd-questions]; FORGED_SENDER(0.30)[grog@FreeBSD.org,grog@lemis.com]; SIGNED_PGP(-2.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:4764, ipnet:121.200.0.0/24, country:AU]; FROM_NEQ_ENVFROM(0.00)[grog@FreeBSD.org,grog@lemis.com]; FREEMAIL_CC(0.00)[gmail.com,FreeBSD.org] X-ThisMailContainsUnwantedMimeParts: N --K8nIJk4ghYZn606h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thursday, 23 June 2022 at 6:03:20 +0200, Polytropon wrote: > On Thu, 23 Jun 2022 13:01:18 +1000, Greg 'groggy' Lehey wrote: >> [...] I personally find that prepending >> ">" to the original message works best. Leaving white space after >> the "> " and leave empty lines between your text and the original >> text both make the result more readable. > > Prepending what? After the what? Seems there is a charset mismatch. Ugh. Yes, you're right. > Or is it just my MUA displaying nonsense (which would be new to me). > Oh the joy of UTF-8... ;-) What happened here was that I copied the text from the (UTF-8) web page into a text that was (I think) implicitly ISO 8859. My copy of the message also shows this mutilation. But strangely, replying to this message, I find that the text has been automatically recovered. It doesn't stay that way: in the editor it looks correct, but the MUA displays it incorrectly. The issue was with the quotation marks, and it should look correct above now. > Otherwise, I completely agree to the concept that form and content > should match, and that form can help a lot to improve readability > and accessibility of information in general. And people shouldn't make the kind of mess that I managed to make :-( Does anybody have an opinion on character set recommendations? I think we should ask for UTF-8 if at all possible. Greg -- Sent from my desktop computer. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php --K8nIJk4ghYZn606h Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAmK0CSAACgkQIubykFB6QiODDACfVJqzU9JuginmRhxAPW8X9wiX BZgAnAiCJmD3EXEykp7IDy06Rq0JR4NY =yNKB -----END PGP SIGNATURE----- --K8nIJk4ghYZn606h--