IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@icann.org> Tue, 05 November 2019 23:10 UTC

Return-Path: <paul.hoffman@icann.org>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2093512008F for <xml2rfc-dev@ietfa.amsl.com>; Tue, 5 Nov 2019 15:10:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 zWflfIFHqqQE for <xml2rfc-dev@ietfa.amsl.com>; Tue, 5 Nov 2019 15:10:35 -0800 (PST)
Received: from ppa5.dc.icann.org (ppa5.dc.icann.org [192.0.46.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8D9C120072 for <xml2rfc-dev@ietf.org>; Tue, 5 Nov 2019 15:10:34 -0800 (PST)
Received: from PFE112-CA-1.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.7]) by ppa5.dc.icann.org (8.16.0.27/8.16.0.27) with ESMTPS id xA5NAXwU013687 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <xml2rfc-dev@ietf.org>; Tue, 5 Nov 2019 23:10:33 GMT
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Tue, 5 Nov 2019 15:10:31 -0800
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1497.000; Tue, 5 Nov 2019 15:10:31 -0800
From: Paul Hoffman <paul.hoffman@icann.org>
To: "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
Thread-Topic: [xml2rfc-dev] [Ext] Re: [Rfc-markdown] [xml2rfc] <br> is back, was: New xml2rfc release: v2.32.0
Thread-Index: AQHViPoqcW3Ou2ALpUa8PUOCNpLyDqdxnNOAgAAHVACAAARTgIAACSkAgAo77ACAAX//gIAAEyoAgAABjACAAAD8AIAAAJiAgAACDgCAAAKNAIAAAPeAgAAJtoCAAAHUgIAAAv2AgAADMoCAADGsAIAAA8gA
Date: Tue, 05 Nov 2019 23:10:30 +0000
Message-ID: <a73c3662-dbbe-57f6-422b-4a2425e94359@icann.org>
References: <E1iGMu9-00055y-Ui@durif.tools.ietf.org> <b19cd7de-6992-a3b5-ea23-929627018cc0@gmx.de> <019a4a58-ca92-0497-1155-303fba341241@gmx.de> <FB3B5D3A-2AFF-4ACE-BD71-D9EE2F9A4908@tzi.org> <4911a729-648a-a6c7-e673-4dd0fc0cadac@levkowetz.com> <908decb8-c24c-238d-2e27-982aa587d321@gmx.de> <0f5b5e73-bcca-0ff5-570d-c1622891dcf8@gmx.de> <703F1E91-C9E0-42BD-927C-D0D65D8CF7B0@rfc-editor.org> <6723154e-9bf1-d8ce-c8bd-a681fec1de5a@gmx.de> <D1535E4D-A260-477E-AF44-720C28801768@rfc-editor.org> <c551753e-7b28-0284-3ef8-bba884ea44f2@gmx.de> <6EAF86F8-C32F-434E-87ED-9E66043CC989@rfc-editor.org> <6c67abbc-542d-f734-d462-658ae8ad0820@levkowetz.com> <a6da4e7f-d82b-8c65-9ff6-477fd0d475bf@gmx.de> <B55B4594-3381-44D8-AE88-57453C418DA5@rfc-editor.org> <951cb208-e942-6b60-ce51-3629a4320e5b@gmx.de> <4B6CDE05-0712-4287-B9DB-953169D2C218@rfc-editor.org> <ba571a31-5853-cb2e-4ed1-2efabdff2470@gmx.de> <345F3DA7-A0A6-4C45-A30E-FF09CA6E76AE@rfc-editor.org> <f0a381f8-bd3c-0750-c7d3-1fc87ccc8dcf@levkowetz.com>
In-Reply-To: <f0a381f8-bd3c-0750-c7d3-1fc87ccc8dcf@levkowetz.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:68.0) Gecko/20100101 Thunderbird/68.2.1
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.47.234]
x-source-routing-agent: Processed
Content-Type: text/plain; charset="utf-8"
Content-ID: <B69CF848EEB92F40B580C6B487D75E1D@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-05_08:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/Bsdc_iw1qE9dWehl9VA9H28-2Lg>
Subject: Re: [xml2rfc-dev] [Ext] Re: [Rfc-markdown] [xml2rfc] <br> is back, was: New xml2rfc release: v2.32.0
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Nov 2019 23:10:36 -0000

A side-effect of the use of <br/> in titles, names, and so on means that searching will likely always then be done on the HTML output, not on the canonical XML. If folks are comfortable with that, great, but it does make one of the output formats more important than the canonical format.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email