IETF Logo Mail Archive

Re: [Rfc-markdown] Trying to mitigate "Re: The <tt> train wreck"

Carsten Bormann <cabo@tzi.org> Wed, 27 April 2022 08:01 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46008C1B1602 for <rfc-markdown@ietfa.amsl.com>; Wed, 27 Apr 2022 01:01:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id znpl9BWxfo5O for <rfc-markdown@ietfa.amsl.com>; Wed, 27 Apr 2022 01:01:49 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFF39C19E0E6 for <rfc-markdown@ietf.org>; Wed, 27 Apr 2022 01:01:47 -0700 (PDT)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4KpB6H6g0vzDClr; Wed, 27 Apr 2022 10:01:43 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <5fa2fbdc-6855-b63d-8392-9bcadbbf6552@gmx.de>
Date: Wed, 27 Apr 2022 10:01:43 +0200
Cc: rfc-markdown@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <79BACE8B-7EF9-4158-894A-2A365FC8494D@tzi.org>
References: <20220427011450.EDBFD3EE73DA@ary.qy> <5fa2fbdc-6855-b63d-8392-9bcadbbf6552@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/oDWxu2mmb_u5-akQvIVVhciAmn8>
Subject: Re: [Rfc-markdown] Trying to mitigate "Re: The <tt> train wreck"
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Apr 2022 08:01:52 -0000

On 27. Apr 2022, at 09:39, Julian Reschke <julian.reschke@gmx.de> wrote:
> 
> What we did not consider was the problems related to what happens in
> plain text output. And that's because back when this work was done, the
> consensus in the team was that the aesthetics of the plain text output
> just do not matter.

But that is not the problem with the 3.11.0 change.  
The problem is that with that change, the plaintext output for certain XML documents now is plain wrong.
(In other cases, it does look better.)

Dismissing the aesthetics was at least an excusable reflex, not thinking about the influence on correctness wasn’t.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email