Re: [Rfc-markdown] 1.3.34: map most codeblock classes to <sourcecode> instead of <artwork>

Jay Daley <jay@ietf.org> Sun, 21 February 2021 19:57 UTC

Return-Path: <jay@ietf.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 13CF73A1069 for <rfc-markdown@ietfa.amsl.com>; Sun, 21 Feb 2021 11:57:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Ul8roOL-4EGi; Sun, 21 Feb 2021 11:56:57 -0800 (PST)
Received: from jays-mbp.localdomain (unknown [158.140.230.105]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 097433A1066; Sun, 21 Feb 2021 11:56:56 -0800 (PST)
From: Jay Daley <jay@ietf.org>
Message-Id: <E9362A07-0057-4DF0-B006-C45149F0FC82@ietf.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_FCF5F385-252A-4CDF-BB2C-B1F766B94F8E"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Mon, 22 Feb 2021 08:56:54 +1300
In-Reply-To: <B8D57CFC-EB4A-4F7E-8614-99F39719183A@tzi.org>
Cc: Julian Reschke <julian.reschke@gmx.de>, rfc-markdown@ietf.org
To: Carsten Bormann <cabo@tzi.org>
References: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org> <20210219072402.GA151175@miek.nl> <77684aa0-dcdb-fc38-8d31-86f2f5ae2ede@gmx.de> <22FFC094-63C4-43E8-8FDA-28832DD7FF28@tzi.org> <B8D57CFC-EB4A-4F7E-8614-99F39719183A@tzi.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/EdEOM22qhJfnVqj1MnI2Os1u4wE>
Subject: Re: [Rfc-markdown] 1.3.34: map most codeblock classes to <sourcecode> instead of <artwork>
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: Sun, 21 Feb 2021 19:57:00 -0000


> On 19/02/2021, at 9:47 PM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> On 2021-02-19, at 09:45, Carsten Bormann <cabo@tzi.org> wrote:
>> 
>> https://datatracker.ietf.org/doc/draft-bormann-core-media-content-type-format/
> 
> Sorry, my intent here is probably better visible in the current editor’s version:
> 
> https://cabo.github.io/mtct/draft-bormann-core-media-content-type-format.html

I’m not sure I understand - do you mean that you want it indented to show that you are quoting the ABNF or do mean that you want a different alignment.  I ask because I can’t see a different alignment.

Jay

> 
> Grüße, Carsten
> 
> _______________________________________________
> Rfc-markdown mailing list
> Rfc-markdown@ietf.org
> https://www.ietf.org/mailman/listinfo/rfc-markdown

-- 
Jay Daley
IETF Executive Director
jay@ietf.org