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

Henrik Levkowetz <henrik@levkowetz.com> Fri, 18 October 2019 14:54 UTC

Return-Path: <henrik@levkowetz.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 B61151208BE; Fri, 18 Oct 2019 07:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.095
X-Spam-Level:
X-Spam-Status: No, score=-1.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 x2p0r1uoeNul; Fri, 18 Oct 2019 07:54:57 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:126c::1:2a]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 513201201DB; Fri, 18 Oct 2019 07:54:57 -0700 (PDT)
Received: from h-202-242.a357.priv.bahnhof.se ([158.174.202.242]:51150 helo=tannat.localdomain) by zinfandel.tools.ietf.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1iLTeZ-0000pr-UQ; Fri, 18 Oct 2019 07:54:56 -0700
To: Carsten Bormann <cabo@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> <b096e29c-02a0-e009-621e-c1eca4712226@levkowetz.com> <4321EEBF-92C2-4405-81BD-899C0FCAC762@tzi.org>
Cc: Julian Reschke <julian.reschke@gmx.de>, "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
From: Henrik Levkowetz <henrik@levkowetz.com>
Message-ID: <5593c2d9-0bb4-93e9-f5d0-babf194340bf@levkowetz.com>
Date: Fri, 18 Oct 2019 16:54:48 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <4321EEBF-92C2-4405-81BD-899C0FCAC762@tzi.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="DxgpL00JHpL0NndIOMnw0STnjSd2irjrF"
X-SA-Exim-Connect-IP: 158.174.202.242
X-SA-Exim-Rcpt-To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org, rfc-markdown@ietf.org, julian.reschke@gmx.de, cabo@tzi.org
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/3fra4mnq3bLQUra_3N7lvqY-m2w>
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 14:54:59 -0000

Hi Carsten,

On 2019-10-18 16:49, Carsten Bormann wrote:
> Hi Henrik,
> 
>> On Oct 18, 2019, at 15:04, Henrik Levkowetz <henrik@levkowetz.com>; wrote:
>> 
>> Signed PGP part
>> 
>> On 2019-10-18 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.
>> 
>> All of the entity references used during the RPC work are converted to
>> unicode code points when the prepped file is produced.  If you see an
>> entity reference in a prepped file it's either a bug or it has been added
>> manually.
> 
> I think that was what Julian was afraid of: Having U+2028 in an
> immutable published RFC.

I'd be more than happy to move to <br/> if we could make that useful for
the RPC.

I think most people who voiced an viewpoint on that was for making it
generally available, but when I proposed how to do that, it seemed to
run into opposition again.

>>> 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.)
>> 
>> It’s been in the xml2rfc distribution for ages.  
> 
> I have 424 files with that name on my laptop.

I'm sorry.  I took the 'I’m not finding the “rfc2629-xhtml.ent”' at face
value.  And yes, it has been changing, it has not been static over time.
I'm sorry if I gave that impression.  I only wanted to point at how it
has been made available.

> These fall into the following equivalence classes (grouped by md5sum):
> 
>  316 1205eb5efbbc8d9a734ba77055388d70
>   88 1aa6d2431ef0219b231913c8fb3c9253
>    2 234420ff1ceb61201fa41655b841513a
>    3 46cad1ba9b921fe41a9102e912073d74
>    2 7a013cd802f0df7e3d9000cd85b9749f
>    2 a66a1389336402406e917908aa6e3255
>    8 cc77bb83d0c9c7c19afd2da03140f1b7
>    3 d2faa8069ff9e2ef2c7c097d2e17cbad
> 
> Of these, I find these in xml2rfc:
> 
>   22 1205eb5efbbc8d9a734ba77055388d70
>    2 234420ff1ceb61201fa41655b841513a
>    2 a66a1389336402406e917908aa6e3255
>    8 cc77bb83d0c9c7c19afd2da03140f1b7
> 
> I didn’t diff all these combinations against each other, but one recent change seems to be:
> 
> <!-- Typographic help characters -->
> <!ENTITY zwsp   "&#8203;"><!-- U+232A RIGHT-POINTING ANGLE BRACKET        -->
> <!ENTITY br     "&#8232;"><!-- U+2028 LINE SEPARATOR                      -->
> <!ENTITY wj     “&#8288;"><!-- U+2060 WORD JOINER                         -->
> 
> And more recently:
> 
> <!-- Typographic help characters -->
> <!ENTITY zwsp   "&#8203;"><!-- U+200B ZERO WIDTH SPACE                    -->
> <!ENTITY nbhy   "&#8209;"><!-- U+2011 NON BREAKING HYPHEN                 -->
> <!ENTITY br     "&#8232;"><!-- U+2028 LINE SEPARATOR                      -->
> <!ENTITY wj     "&#8288;"><!-- U+2060 WORD JOINER                         -->
> 
>> If it's desired to make it
>> more widely available, I’m sure we could do that.
> 
> I was looking for a statement about the definitive source (and thus the definitive version), not a 425th copy…
> 
> (It also should be put into the RFC-editor’s /authors directory, so that the authoring-RFCXMLv3 files there can be validated.)

Agreed.

	Henrik