Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] <br> is back, was: New xml2rfc release: v2.32.0

Carsten Bormann <cabo@tzi.org> Fri, 18 October 2019 11:56 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 36AA112021C; Fri, 18 Oct 2019 04:56:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-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 BpI84d0KR_zE; Fri, 18 Oct 2019 04:56:14 -0700 (PDT)
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 558F51200D7; Fri, 18 Oct 2019 04:56:14 -0700 (PDT)
Received: from sev.informatik.uni-bremen.de (sev.informatik.uni-bremen.de [134.102.218.54]) (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 46vkyN56Ylzylv; Fri, 18 Oct 2019 13:56:12 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <7726840d-e51c-55a1-7cce-69574ec27b6c@gmx.de>
Date: Fri, 18 Oct 2019 13:56:12 +0200
Cc: Sandy Ginoza <sginoza@amsl.com>, "HANSEN, TONY L" <tony@att.com>, "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>, Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mao-Original-Outgoing-Id: 593092570.458542-5d6d43c7b5bbe2f200b91d774fa1ff49
Content-Transfer-Encoding: quoted-printable
Message-Id: <669D5F65-063D-449D-A52A-725D0C9F30DA@tzi.org>
References: <E1iGMu9-00055y-Ui@durif.tools.ietf.org> <8304e61d-c550-91ea-9e23-eef2cd31240b@gmx.de> <A3513970-EEB0-4DBD-9E6F-A87EBFAF886D@att.com> <de4feaff-8f71-cd38-545c-2d848749251b@levkowetz.com> <f00a671a-6fe4-f5ae-2582-0b78ffa1c256@gmx.de> <1f18382c-d830-b887-f5d3-3f376ae4fdd7@gmx.de> <B15F7AF0-F5A0-401A-9F6E-F7E0E466B6A7@amsl.com> <f4f1b7ba-127a-fbfa-531b-eeff03814281@gmx.de> <71bc8d39-d06c-d900-cc8e-04a48218d75f@gmail.com> <0905DADC-E9D5-47A7-B610-F8A62686D2BD@att.com> <07DBAE10-D1FA-45C4-B7A2-321B265CA302@amsl.com> <694c9244-98ae-1e64-39ef-8756d48b36ef@gmx.de> <860c663b-744f-a033-cc50-96088bb1b33c@gmx.de> <04DCBCE3-2C8C-4B03-9081-EF2B7A5C6087@tzi.org> <7726840d-e51c-55a1-7cce-69574ec27b6c@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/ePy18HuIa_ggckkcpgRcFiK3XE0>
Subject: Re: [Rfc-markdown] [xml2rfc-dev] [xml2rfc] <br> is back, was: New xml2rfc release: v2.32.0
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: Fri, 18 Oct 2019 11:56:16 -0000

Right.  I forgot that the XML file in /authors appears to be authoring-RFCXMLv3, not publishing-RFCXMLv3, so it is not indicative here.  (It still has &nbsp; which also needs to be expanded.(*))

Grüße, Carsten

(*) 7998 appears to be mute about native encoding vs. character references.

> On Oct 18, 2019, at 13:42, Julian Reschke <julian.reschke@gmx.de>; wrote:
> 
> On 18.10.2019 13:33, Carsten Bormann wrote:
>> On Oct 18, 2019, at 12:36, Julian Reschke <julian.reschke@gmx.de>; wrote:
>>> 
>>> I note that there is one XML in AUTH48 using this (RFC 8668), so this
>>> really is a bit pressing.
>> 
>> This uses a &br; entity reference — we can easily change that entity into “<br />” later without touching the XML file :-)
>> 
>> (I’m not finding the “rfc2629-xhtml.ent”, so maybe that already is the case.)
>> ...
> 
> That's an interesting idea, but it would be in conflict with
> <https://greenbytes.de/tech/webdav/rfc7998.html#dtd-removal>;.
> 
> Best regards, Julian