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

Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 05 October 2019 21:57 UTC

Return-Path: <brian.e.carpenter@gmail.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 8E35912013D; Sat, 5 Oct 2019 14:57:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 ZOpRTDcL4FGm; Sat, 5 Oct 2019 14:57:07 -0700 (PDT)
Received: from mail-pl1-x634.google.com (mail-pl1-x634.google.com [IPv6:2607:f8b0:4864:20::634]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9E3C1200F3; Sat, 5 Oct 2019 14:57:07 -0700 (PDT)
Received: by mail-pl1-x634.google.com with SMTP id d22so4890032pls.0; Sat, 05 Oct 2019 14:57:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=6XX4b+7L/CV3e3SvyhuPRCT0VFMU6DhWxEzaSSkme0k=; b=Ku0Ny9q4hTDYmDpINLzuldKFBamBdL/81XYWfjZNQ6EDD6/OCZbQsscFIbJtRngZOu tGoJ1B1btKWA2GLQk1e3t+vd50YwUOLciViO7+HjL1rmmeITD06T5c4O9PI70KQvAgWn 23rCGdZBHFM5cQd9frn885IaB3YKsd1V4urUyZ7yV16bHsko/MQne23WSPUxeOMomgb3 T+JeNdFoZI3zzX+5o7vhX/E+Q4rpPkrBZWeRleSYNq/dxvUmMcjIgpI9NyfEjt5+YFOZ aQuIRmHshT5BFwvaTIVxG/mUZQNn6DvvlfmjKTCBiWibbLBsJxO0xj50WAd0nWQEEtyw vdaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=6XX4b+7L/CV3e3SvyhuPRCT0VFMU6DhWxEzaSSkme0k=; b=QqH43HSt22AcDwyckGEmPtzWy4V6lcZEScgrTHPCuNwT5Q3XnU8yKOlrjaD9t2+7SN ZNL6B2xRfX220CSwinA6zoptRkC/qrOOBaxTzHhD/lMDmVdAqsU826uiCxIqpYPCgg38 +T1l3OKdyPQx3++y+byZWq90docl3H6wEbXP/GWBXvSZ/fgjVO2ld1+FNGeXrG6rbIyv bEdJzynCLgdZ7iZRd6MtDT55NcWPl2ocMw9BNBd0x0izVKXV9l7wbKtw6OJzH9qe0PwL pxIsajk+eaD/LRSOQfvIufAOT0UM7VmHJBPPhOGZpve4zxvPlGshh0MTPuUnNMs2Iyho ewfw==
X-Gm-Message-State: APjAAAXGp4b3/FDz8LF8USQXwHAdRjv+nEXxwLFCG19Vg+e7zC3Wsmhu Tvumd6ePArgB9UcM+FthrP5ONSQd
X-Google-Smtp-Source: APXvYqwNUFEgPEtiv5bwdl4Hrbk11gCNOiujRwtIxHabHuzwKjZDkt4XietTjkvaW5s613ggoE+rTg==
X-Received: by 2002:a17:902:9f83:: with SMTP id g3mr22778981plq.154.1570312626783; Sat, 05 Oct 2019 14:57:06 -0700 (PDT)
Received: from [192.168.178.30] (233.148.69.111.dynamic.snap.net.nz. [111.69.148.233]) by smtp.gmail.com with ESMTPSA id p11sm9505903pgb.1.2019.10.05.14.57.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 05 Oct 2019 14:57:05 -0700 (PDT)
To: Julian Reschke <julian.reschke@gmx.de>, Sandy Ginoza <sginoza@amsl.com>, "rfc-markdown@ietf.org" <rfc-markdown@ietf.org>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.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> <20191005061759.GA23541@miek.nl> <61b8704b-3fbd-8148-1e85-909d268377ad@gmx.de>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <b3bc589c-1bb7-5c3a-a273-65fadb26ccaf@gmail.com>
Date: Sun, 6 Oct 2019 10:51:40 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <61b8704b-3fbd-8148-1e85-909d268377ad@gmx.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/wsLaM5m6zl91-iFcD39WWCqwPSk>
Subject: Re: [Rfc-markdown] [xml2rfc] [xml2rfc-dev] <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: Sat, 05 Oct 2019 21:57:10 -0000

On 05-Oct-19 20:40, Julian Reschke wrote:
> On 05.10.2019 08:17, Miek Gieben wrote:
>> [ Quoting <brian.e.carpenter@gmail.c>; in "Re: [Rfc-markdown] [xml2rfc]
>> [xml2..." ]
>>> I'm a bit confused: https://tools.ietf.org/html/rfc7991#section-2.12
>>
>> There was a long discussion on limiting <br> for use in table *only*,
>> after that was written. More discussion ensued and <br> was outlawed in
>> the entire document. And now we are here.
>> ...
> 
> Hmm, no.
> 
> RFC 7991 only allows <br/> in table cells. The long discussion you are
> referring lead to the removal of the element. See
> <https://github.com/rfc-format/draft-iab-xml2rfc-v3-bis/issues/37>;.
> 
> Best regards, Julian

Yes, well, as far as I know RFC7991 is the community consensus (it's an IAB stream document, formally). So I don't think we are done with the discussion, if the RPC is now saying there are cases where <br/> would avoid using a deprecated Unicode codepoint. Maybe issue 37 should be reopened.

    Brian