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

Julian Reschke <julian.reschke@gmx.de> Tue, 08 October 2019 18:36 UTC

Return-Path: <julian.reschke@gmx.de>
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 F12541200B9 for <xml2rfc-dev@ietfa.amsl.com>; Tue, 8 Oct 2019 11:36:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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 (1024-bit key) header.d=gmx.net
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 DO04znOQf8yJ for <xml2rfc-dev@ietfa.amsl.com>; Tue, 8 Oct 2019 11:35:59 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (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 B4649120071 for <xml2rfc-dev@ietf.org>; Tue, 8 Oct 2019 11:35:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1570559735; bh=zOHuvcj3v1+1Eno2YrUMCkQqTymLOrMrkqIEho3eIW4=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=ew80Cjm33XdY75EzgFOVj/Tq8N3RjNgP/0KydcCkMt8V2/67R/+XmPH5cIwZrt8FQ nDJ9rEsin4T282Y854lbfkbKvV7iR7o2HGo4fFMVamvF4YCuOVLsMfm8HsGpEgQR+y 4owydmHiENn/yNw84P261HCmGJ1U9uN7Sh0CQE8Y=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.124] ([84.171.144.80]) by mail.gmx.com (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1M7b2d-1iATH82fpl-0084lj; Tue, 08 Oct 2019 20:35:35 +0200
To: Henrik Levkowetz <henrik@levkowetz.com>, Paul Hoffman <paul.hoffman@icann.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>, Sandy Ginoza <sginoza@amsl.com>
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> <c88388ff-84ae-c5f5-e093-e9aee77da3d6@levkowetz.com> <5f467e5a-200f-e7fd-94d6-8b04d863c7e2@icann.org> <b3c2d77e-d28e-3b3e-8fe7-88c91104410d@levkowetz.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <c22a5004-7dfa-a724-1f26-c68272d4d121@gmx.de>
Date: Tue, 08 Oct 2019 20:35:33 +0200
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: <b3c2d77e-d28e-3b3e-8fe7-88c91104410d@levkowetz.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:a43NUiA7VesJZD1NumULz3ipelu6k0riF/oN2AUFvRzV3c5mWeD q8ay01Q1kY5a7fbzynIwc3irctJ9IKq6jRdQ7JucWB075U6bPOKpNmEYcxbm0KtboGpcJT5 w45BHQBDLMI/I1LMs2zM+r1ar26AqaYcGxQ5f4MHPazuRtwBF6jsYB9K1rKcjGRGe4TmCxd kCGL3qhquwjZYEVN1lrXA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:wDEbmoS9rsM=:4VxXx1dAatojV00FGWsgec X/BUIFtS4ZKWg+fdwawuNS+U7Br5cBGy3EVsdOymd2cyN+ccLo9qzGIyYobd4c8rSj2c9UOEP s2wpTeM+Z2tuAsrSW86yVgFK05+8LwYO8tWWPmy7BcHr+6S4xGSw1EonFG9CD98Tbxi/wTb5B 0FerTHCdcvIM2P9sINcuyJUT1IvImQUdY/O1viIgbB7x3E6uRU6K8H1XL4tP1Y+wwG3JE3M0K 1S6pWmXNHgCcRkovAabL7Jc/A6QDnBQWTKeFljW+Uwr07i/30aAgC1FJqcNln/ZMYFLYxA96E a83Em4zU2PvpIlIPcPF4aubdn5ZlqCiccuIRmoDTn2WHWB8w4yChVKFG01hAHWw9ty6DNzWfT fOQAHr3QzpwH7u23CKFx8hNYhzMosT7FmkB8nvapt06RQpwlfLAD5+qpNv4de1yO/KSLKAij7 fwUPd4OZfQeApWni0frmbUnQoPmFzbP20nHPDsLjTWrDZW9+MfJtcsasUzW469IM+M5sKLn/3 RjkGXCDNjYhd/jTjgF0WlzpwfPwyw87I8Oj0uP1jiCVO57XmixRQMvpqJ4VUISVMy6aCyR6ip Lre2KzXdF/QD8J3mY55w+UQoT/T18N2ahETLchWq+SvdlbJapvtCjB86r0g85In2SedIefs5X edwuABPDGMCEfMD847Ntlg1ewaQCVUm9M/sVCcnoD7HkTL9d8WHhGPopgDU5qCbnsOdZl4yWm 5hjGdpuPLA6tVfzxz6WyubRTuusZMU63/3l5Nu+fVRSr8E2WMEQyJ7m0gY3su7AaETe+lSxWI dB1P0OpnVX3drLEnatk/FKTY6L+cczOh2B4ECp+tiI8rPS7uX4YeYiwAbn3i+aryE15N6HTQ/ x73dDFPXGbhuYsB1c27incuhxqbyKnxScJoWAXskmxnmnmg64pMuMOzBkISLTjk8BDk3KZs6z pdAHdHjRmjP1opLHJ+DM/cTOVvKudUupOOAQHCE63OJ6NCVTgB/KXhOIOIWr0gFfm3mCDw1PC +Y9GJy1aN4P9kq45iFlSeKAjGuE0sEWCTFzcPAu/VZr8tg5Hzp98KmQdjSndF5aGC8MWTdWmn Q++J8ozw8syYjWmHj7PUeYkuDRyB2lwO+JFvwezuDPhvtczbIrcYcnYuBycT07pcbz5+jHT7P h46jgjlEOhnTDiM+Qzhh3t8Nc8VKr4xgAEK7SCOT69k0I6SAKH+khLFL1XZDjmgDcEtkPbSw6 6UArYpuRY2UoyrRW+zpou93B5RKHY1+yBDz/PnURfOZyGzWTOrrrqkatI4E4=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/gVMSlwVn_ctRKOweXHTjoepQ0gg>
Subject: Re: [xml2rfc-dev] [Ext] Re: [xml2rfc] [Rfc-markdown] <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, 08 Oct 2019 18:36:02 -0000

On 08.10.2019 19:51, Henrik Levkowetz wrote:
> ...
> ... > So that removes dt, em, strong, title and tt.
>
> <title> is one of the cases the RPC already ran into, so eliminating that
> from the list will leave one of their cases unhandled.

That may be true; but then, it would be awesome to understand whether
this was about:

   1. *not* breaking the title in a specific place when the title was
too long, or

   2. breaking the title because it really consists of two different parts.

For case 1) I think the "old" approach of just using &nbsp; between
words not to be broken apart is better. For 2) I'll claim that <br/> is
not the right thing to do; <subtitle> might be a better fit.

> The case I made in the original issue #37 still holds:  Limiting <br> too
> strongly will result in a lot of surprises for authors, when they expect
> to be able to use <br/>, but the validation fails.  I think this is
> applicable for em, strong, and tt.

No strong opinion here. I don't believe that we need them inside these
elements, though.

> Additionally, the case Sandy mentioned where the author wanted a piece of
> text set on two lines is very likely to come up for <tt>, so not permitting
> <br> there seems wrong.

Would that be

   <tt>a<br/>b</tt>

? The same effect could still be achieved using:

   <tt>a</tt><br/><tt>b</tt>


> As for dt, it will have similar issues as <title> and <name>.  It will only
> become an issue when the RPC runs into a case where there's a long <dt>
> text which doesn't display well without <br>.

Are the expectations here the same for HTML and TXT output? Do we have
an example?

> I think the right thing, both for the RPC and authors in general, is to have
> <br> available everywhere they might end up using it, rather than restricting
> it too strongly.
> ...

Well, if we do, we need to define what happens when the content is
referenced somewhere else (xref, reference, ...).

Best regards, Julian