IETF Logo Mail Archive

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

John Levine <johnl@taugh.com> Wed, 27 April 2022 01:15 UTC

Return-Path: <johnl@iecc.com>
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 05003C1850F3 for <rfc-markdown@ietfa.amsl.com>; Tue, 26 Apr 2022 18:15:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.852
X-Spam-Level:
X-Spam-Status: No, score=-6.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=SEfKqnbh; dkim=pass (2048-bit key) header.d=taugh.com header.b=J2nOmaY1
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 wXLVRKkn9Up5 for <rfc-markdown@ietfa.amsl.com>; Tue, 26 Apr 2022 18:14:55 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 2E505C1850C3 for <rfc-markdown@ietf.org>; Tue, 26 Apr 2022 18:14:54 -0700 (PDT)
Received: (qmail 53919 invoked from network); 27 Apr 2022 01:14:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=d29c.6268990b.k2204; bh=mbJQVTqoKgyOA4uX0A8e5U0xcMlPOQwN3NHxl0Tm90k=; b=SEfKqnbhYjcqY6jSD1PJZUCgL+jssed1kIZl8hwtnJeleD/iavLw647dHmy5dG4fvfj4gY7BCpwNPSD+jD5DT/hz3cfzvwM8RpcOVY4+jhqNged18GFcw1jhTQj72vn4pfbaHSgmPj10B7vTit97f4eEeMXyqQcaJQ2iMFAE70WQ9jtBf597EmPIN1JHxC3ZaYN/EsGFBMOcaECtiLlAd2P+ksoN3o1Lf0Xy2aOWRowWv25AHzCT+L+woVNgOdmU+mfV6/b6tGzks/jf1OcWu6MQYtChdimtOX6XbY34ncoHf1ATFlmtpE73i7THWlisvJuRycZFrakS2uxrFnK2zw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=d29c.6268990b.k2204; bh=mbJQVTqoKgyOA4uX0A8e5U0xcMlPOQwN3NHxl0Tm90k=; b=J2nOmaY19T1PKF22L8S2Xoalc137M/bbl8lKkWUp0hgszHkVt1ARa0cfUmjL5NHhdfyeDp6w07n0SHCE091/lLzF4+ysAie+0L9Hew/pZRrZkbP0MkWz/FlNb5OQZspei9n3N4TX8QgJ6sZVte5qHZj+1Cf5LfLDaHUoJmUlw5z0doM2lP5QaIiY5eQx7LJ5X0+olMKzh33mt+kYo157gTVvoXVvcuB9saiG7HXXsCQOT6ccMAI/FyVdNdIcbFsaiBOIm/H8c+jzbrlJtJ/SRxXRoXL/PJftWAjhccNIIDfyBu2ybffwQBALBq1B3qJmwFXrpc+g7eKQrzeRJaCSMA==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 27 Apr 2022 01:14:51 -0000
Received: by ary.qy (Postfix, from userid 501) id EDBFD3EE73DA; Tue, 26 Apr 2022 21:14:50 -0400 (EDT)
Date: Tue, 26 Apr 2022 21:14:50 -0400
Message-Id: <20220427011450.EDBFD3EE73DA@ary.qy>
From: John Levine <johnl@taugh.com>
To: rfc-markdown@ietf.org
Cc: cabo@tzi.org
In-Reply-To: <F4C29CED-87A8-40B8-BE28-4EF54CEA3A8B@tzi.org>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/MDgZGprY-7wrAHIw4EJl8W791Jc>
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 01:15:00 -0000

It appears that Carsten Bormann  <cabo@tzi.org> said:
>Clearly, there are cases that benefit from this change (where <tt was decorative only and no information was needed in the plaintext version).  Where <tt was
>semantic (not to be lost in plaintext), ...

I think that <tt> was clearly a mistake, since it has no semantics anyone can describe.

Rather than trying to fix it, since we're about done wrapping up 7991bis, how about 
thinking about some semantic tags that actually say what <tt> sort of hinted at?

R's,
John

v2.23.0 | Report a Bug | By Email