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> Fri, 18 October 2019 18:29 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 5E760120912 for <xml2rfc-dev@ietfa.amsl.com>; Fri, 18 Oct 2019 11:29:22 -0700 (PDT)
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 FB8RgPUqbpb5 for <xml2rfc-dev@ietfa.amsl.com>; Fri, 18 Oct 2019 11:29:20 -0700 (PDT)
Received: from ppa3.lax.icann.org (ppa3.lax.icann.org [192.0.33.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 B99F41208E5 for <xml2rfc-dev@ietf.org>; Fri, 18 Oct 2019 11:29:20 -0700 (PDT)
Received: from PFE112-CA-2.pexch112.icann.org (out.west.pexch112.icann.org [64.78.40.10]) by ppa3.lax.icann.org (8.16.0.27/8.16.0.27) with ESMTPS id x9IITJfv001421 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <xml2rfc-dev@ietf.org>; Fri, 18 Oct 2019 18:29:20 GMT
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 Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 18 Oct 2019 11:29:18 -0700
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; Fri, 18 Oct 2019 11:29:18 -0700
From: Paul Hoffman <paul.hoffman@icann.org>
To: "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
Thread-Topic: [Ext] Re: [xml2rfc-dev] [Rfc-markdown] [xml2rfc] <br> is back, was: New xml2rfc release: v2.32.0
Thread-Index: AQHVhd+uHWJz2PU7j0+8nKQcJlkbAadhLYAA
Date: Fri, 18 Oct 2019 18:29:18 +0000
Message-ID: <755cea57-d3a8-cfd8-a621-69d931e90991@icann.org>
References: <E1iGMu9-00055y-Ui@durif.tools.ietf.org> <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> <5593c2d9-0bb4-93e9-f5d0-babf194340bf@levkowetz.com> <6BF7D165-EA48-44C1-9153-3F011058561F@tzi.org> <7088451e-745b-a31b-88fb-bce9cb48696a@levkowetz.com> <efb58534-8112-2303-1967-536daae9ff51@gmx.de> <34FFD9FB-7D0A-4BEE-9BAD-AFBD7F883CE6@amsl.com> <b43d1d27-b193-795b-c3c3-7b652039fdd3@levkowetz.com>
In-Reply-To: <b43d1d27-b193-795b-c3c3-7b652039fdd3@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.1.2
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
x-source-routing-agent: Processed
Content-Type: text/plain; charset="utf-8"
Content-ID: <2252D1BFA20FD24986585EEFFE99B1FF@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-10-18_04:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/hWxlWaRTpagSOxPMzZxdJwTWcEA>
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: Fri, 18 Oct 2019 18:29:23 -0000

On 10/18/19 11:12 AM, Henrik Levkowetz wrote:
> So, how would you handle the first of my two examples in an earlier message
> in this thread:  The title of my implementation notes draft, which requires
> more than one line both in text, html and pdf rendering:
> 
>                       Implementation notes for RFC7991,
>                      "The 'xml2rfc' Version 3 Vocabulary"

This question presupposes that where a title is broken in a particular rendering is important. RFCs 7792, 7794, and 7795 did not indicate any such importance in their discussion of titles. In particular, for the HTML rendering that most people focused on in the discussion that led to the v3 format, line breaks are explicitly unimportant because the rendering might be on a narrow screen. It sounds like this issue is being brought up despite the text in the relevant RFCs.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email