IETF Logo Mail Archive

[Rfc-markdown] 1.3.35: revert to <artwork> if "artwork-align" is set

Carsten Bormann <cabo@tzi.org> Thu, 18 February 2021 20:48 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 3DB373A1836 for <rfc-markdown@ietfa.amsl.com>; Thu, 18 Feb 2021 12:48:54 -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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 qZaXs0aMqa2k for <rfc-markdown@ietfa.amsl.com>; Thu, 18 Feb 2021 12:48:51 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 023F43A184A for <rfc-markdown@ietf.org>; Thu, 18 Feb 2021 12:48:50 -0800 (PST)
Received: from [192.168.217.118] (p5089a828.dip0.t-ipconnect.de [80.137.168.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DhRdD2GBWzydD; Thu, 18 Feb 2021 21:48:48 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org>
Date: Thu, 18 Feb 2021 21:48:47 +0100
X-Mao-Original-Outgoing-Id: 635374127.663709-3124b8a1abcbfc968107083fe444bad0
Content-Transfer-Encoding: quoted-printable
Message-Id: <A9733C7C-F4EF-4FAD-A9C8-C4CD7DA87660@tzi.org>
References: <4E1735EC-A5DD-4201-A6EA-2285D5CC9C21@tzi.org>
To: rfc-markdown@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/JtuXARpMGAX8FctdRNb_EAXL2Po>
Subject: [Rfc-markdown] 1.3.35: revert to <artwork> if "artwork-align" is set
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: Thu, 18 Feb 2021 20:48:54 -0000

Bizarrely, RFCXMLv3 does not allow an “align” attribute on <sourcecode>, while it does on <artwork>.  This, together with the automatic assignment of <sourcecode> to appropriately classed code blocks added in 1.3.34, creates a backwards compatibility problem.  

This is now worked around by reverting to <artwork> for any code blocks that do have “artwork-align”/“sourcecode-align” inline attributes, regardless of type.
So if you want your source code to turn up as <sourcecode>, do not center/right-adjust any more.

We apologize for the inconvenience.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email