IETF Logo Mail Archive

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

Miek Gieben <miek@miek.nl> Mon, 25 April 2022 12:09 UTC

Return-Path: <miek@miek.nl>
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 A206E3A1825 for <rfc-markdown@ietfa.amsl.com>; Mon, 25 Apr 2022 05:09:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=miek-nl.20210112.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S5cDjJWNoHs5 for <rfc-markdown@ietfa.amsl.com>; Mon, 25 Apr 2022 05:09:26 -0700 (PDT)
Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 397B63A1826 for <rfc-markdown@ietf.org>; Mon, 25 Apr 2022 05:09:25 -0700 (PDT)
Received: by mail-ej1-x62a.google.com with SMTP id l7so29230219ejn.2 for <rfc-markdown@ietf.org>; Mon, 25 Apr 2022 05:09:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=miek-nl.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=WsPsXogtzhYQQy9xvYeWLorqR6HYDU2yRWlsWLHaui8=; b=2EcHgv3AH58R0VQHLjfZrU+J8kTm8xCdNaTb5/ul8EB0/ys+PYy3DEOX6tvgTuHoQL aVbrFCptqV85lfdQK5J8VW8Hwrf580Y7uyOSVykRkYLbqr661NyBryxqRWe7tRtsUn95 X37OzAPqhjLZWSSxuZlpOhDcMfBNj9FaOvNAGGPgGD3o1Q9m/fAf6mozzrmO00HLN2Oh Zu0kbzQDIQj1nQAfyD3uEZDn6W2nhJyTpsFLNPssfeTasVk8Ukeyb38/IgCIwTH9cd0A uCYbVqzH2RY9eMfNoy0W20rvS2pmyH88/7+yEiLy6ElSN0aPJZsGjW2dU5TJ1S0DcOKV Q7Mg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=WsPsXogtzhYQQy9xvYeWLorqR6HYDU2yRWlsWLHaui8=; b=eWXJ6YimagozQP3lX+8FU1G8OcrZo8xUSBI3QOlALqV/UjOIyIuSCI7Ow8hX7xyW2/ ItKt7GF1rGNM1jwgdNHzOnYpUMyJt8p9yYsxn9hf2ep+qkhrWyh5y/A4ux5EyumdzeWT 4nGpe7HwXx/4Jnf9h4qYNtqwlusDLdrw+1FP6h5oIr37RaGXi+iQG7oV0cC+rOEAE217 Ui6yEluKF76/XaF02fqobsbk9kBLlr7Sz2jLeHcLZQRnfv3/yoVHauROO3F6yQHp1zso +I3XFJvUu45KLwmgcvN9vBWUTIwIp72bO+uf0oBySTyv8pN1rTlmaIswYQHsD/OBtySv U+1A==
X-Gm-Message-State: AOAM5339Tt7DHXo2AsHZj9tETyixmTOKDEC+FPzRqdmT5GL5Zh3l3AhG E9Tc+qpW1NFh4xDt1Hg3enMXCg==
X-Google-Smtp-Source: ABdhPJzn+vAn+w0RjtFrLKxvETGxLOVPtecJNQzQqPdsUA99UWXFutB0sLPgK/u9VpwsQylFlfZnTw==
X-Received: by 2002:a17:906:4fc8:b0:6d8:5059:f998 with SMTP id i8-20020a1709064fc800b006d85059f998mr16294342ejw.487.1650888563936; Mon, 25 Apr 2022 05:09:23 -0700 (PDT)
Received: from miek.nl (dhcp-077-251-206-042.chello.nl. [77.251.206.42]) by smtp.gmail.com with ESMTPSA id le4-20020a170906ae0400b006f38734cadbsm1759724ejb.136.2022.04.25.05.09.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 25 Apr 2022 05:09:22 -0700 (PDT)
Date: Mon, 25 Apr 2022 14:09:21 +0200
From: Miek Gieben <miek@miek.nl>
To: Jay Daley <exec-director@ietf.org>
Cc: Carsten Bormann <cabo@tzi.org>, rfc-markdown@ietf.org
Message-ID: <YmaPcb7r/2DTto20@miek.nl>
Mail-Followup-To: Jay Daley <exec-director@ietf.org>, Carsten Bormann <cabo@tzi.org>, rfc-markdown@ietf.org
References: <04BFB6A7-7601-409D-8101-237242F6F38A@tzi.org> <F4C29CED-87A8-40B8-BE28-4EF54CEA3A8B@tzi.org> <834B1392-281F-4F60-A05B-AC49D8FF208F@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Disposition: inline
In-Reply-To: <834B1392-281F-4F60-A05B-AC49D8FF208F@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/bYkGQImoNvXE_iOvIY3R7x9P4Ig>
Subject: Re: [Rfc-markdown] Trying to mitigate "Re: The <tt> train wreck"
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 25 Apr 2022 12:09:32 -0000

>In many flavours of markdown, including GitHub, triple backtick is used to indicate multi-line code blocks (code fences) and single backticks for code spans.  You appear to be switching the two.
>
>Also, how do you see this intersecting with this discussion that we had: https://github.com/ietf-tools/xml2rfc/discussions/753 about a possible <term which lends itself much better to semantic markup.

I was leaning towards "*`term`*`, i.e. wrap the backtick in emphesis and then output the
new element (if xml3 goes that route).

Of course if we get a <term type="xxx"> sort of element, setting the type from markdown
will be difficult.

/Miek

--
Miek Gieben

v2.23.0 | Report a Bug | By Email