Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issue, RFC 7991, In Section 2.12, <br>

Julian Reschke <julian.reschke@gmx.de> Wed, 03 October 2018 11:39 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 12DB51310AE for <xml2rfc-dev@ietfa.amsl.com>; Wed, 3 Oct 2018 04:39:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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 FK3wDfCrKaQ3 for <xml2rfc-dev@ietfa.amsl.com>; Wed, 3 Oct 2018 04:39:25 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (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 A1E17130EDB for <xml2rfc-dev@ietf.org>; Wed, 3 Oct 2018 04:39:24 -0700 (PDT)
Received: from [192.168.178.20] ([84.171.148.77]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MBnSJ-1fyYx31dhf-00AnIP; Wed, 03 Oct 2018 13:38:42 +0200
Received: from [192.168.178.20] ([84.171.148.77]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MBnSJ-1fyYx31dhf-00AnIP; Wed, 03 Oct 2018 13:38:42 +0200
To: Henrik Levkowetz <henrik@levkowetz.com>, Paul Hoffman <paul.hoffman@icann.org>, "xml2rfc-dev@ietf.org" <xml2rfc-dev@ietf.org>
References: <E1g6wQ8-00057n-85@durif.tools.ietf.org> <70ee4cff-7533-13e0-d71a-ffecf2dc56f0@gmx.de> <24828f94-dbbd-4c18-8d85-333487bda367@levkowetz.com> <3ac63652-2df2-03c7-eee6-bad2cbd326d8@levkowetz.com> <1BA3E011-CEB3-4F56-9CB5-599C6D2D8A5D@icann.org> <2a71916e-4704-ef8c-b9bb-0cda1781c706@levkowetz.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <2a06b7c8-5a84-60eb-c96e-25d07c61d67f@gmx.de>
Date: Wed, 03 Oct 2018 13:38:36 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0
MIME-Version: 1.0
In-Reply-To: <2a71916e-4704-ef8c-b9bb-0cda1781c706@levkowetz.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K1:PWCITLXvXhNgbnqL3Ylu234VSC/Rm5RoTARcx468tk1+g2mlv03 5vmEtfuw0f5RlX/hI3f3M9d/ITAcgeOV8f7Tr1yEPOOZpZHz15z9CJ4gPZnPVp/gcqFkQQ+ 4RDgWlOllqNw1PYFe30BWPa9vTrf8+4zdzQg1omke06lyVtnfdSRiBtMEY0zOwm5HAaq4H2 A/Ju647cB9iz7OJ+1qLNg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:iASn3rk9Wfs=:jeaM3OHMMDBBl5FNI0BCvY bZ9P62zcsX+MTLI8NCEVM3L38Qza0nTlEs5br2xJg87BmaK2pSa/E0T3fWBLiJ/6mnE7ZknII Fs6uUoHEFCm2lEvXfBnXQcjTvUDFnFmbv78YiQx4w14P8MRy1Zj5WsB7v5QkoSt3sU7oPjXVC 2WJ+t/hXc9t97eqp3Kemvrz+6Vwousb42MSfqUhVb7VUAarHEHhUEAYgP4y5RKM/wEy+hZ1r2 y/in3x80AfAOoUpIUlB5IZVJ3aQ3AYMdQSUoWzaY0Y0vlXEcYDAHYn+AxM7g/NvVeYJE8derg 8lNSC4DtQWcK1PAllGBRcI+yPqdN5W9lJ3Hhqxd+4Q6kyOrYjMsvW5CCR7JONR1xXlXkJAlFf vwhA+aK+bkPzcfk8DONSmR5z0ZBcKm0t+Q7ox7cYl5+sZdX0s1nh05UuAaA0QpIRTdedZjxrP L+c9xEgi19XRAOJODyidhERCnZIU1iIkY1Qh44Lcl73BCOQIS445Ir3wX+AnYL/8kXerqqQMA UOQfwvxNVpkQ0SqGYnI4Nww/QxGtnQrTbfVq5XYiBMVut75VQE60ZWyLkFcSmrz0YzpEYyCyd DwSg/G4oaR2em40BvVit9kUN+36nV5Dd1KDBsoEMgghMKdEYHo5YkV67izzzI8v9p69gEPvxA IuhQmIj8CYVlB3lP6EizodMR5nDc5Vr6QsV+ryvOqBteaELHKiBIXyG391aiUut7K97qLSJBK gpxV3b3ZD5hi0TSOU3mRmGkHBqAMy1ZyLo5UTpLjUYYySDrfuAcqnZ49CZ4ldgSkbNiU/uWc8 KBAqsAaJ3xN5GZCJHh1nU1HI1bgA0UfkB5UeNj9qL64lpMaemI=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/PrDjUgdA3Vy3X-JceNJBItclDyI>
Subject: Re: [xml2rfc-dev] RFC 7991 issue #37: Schema Issue, RFC 7991, In Section 2.12, <br>
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: Wed, 03 Oct 2018 11:39:27 -0000

On 10/3/2018 11:25 AM, Henrik Levkowetz wrote:
> ...
>> See Julian's response in the thread above. The WG decided
> 
> Umm?  Which WG? Could you point at the discussion?

"Design Team".

>> that it
>> didn't like <br> because it causes the author to expect things that
>> might not be true in all renderers, such as in the middle of section
>> headings, as a run of <br><br>, and so on. However, there were many
>> use cases for line breaks within a cell in a table because of the
>> limitations on the horizontal space in cells.
> 
> I don't see this.  I think that if there are considerations which makes
> <br> useful in for instance a 30-character width context which don't
> apply in a 69-character width context or a flowing-text context on a
> narrow screen, they need to be laid out explicitly.

How did you arrive at 30?

Table cells can get very narrow, like just a few characters, and in that 
case it can be desirable to control line breaks.

FWIW, HTML5 *allows* <br> in many places, but says clearly that it's 
only to be used when the line break has semantic meaning, such as in a poem.

Best regards, Julian