IETF Logo Mail Archive

Re: [xml2rfc] subsection failure

Carsten Bormann <cabo@tzi.org> Thu, 23 April 2020 22:41 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: xml2rfc@ietfa.amsl.com
Delivered-To: xml2rfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55F023A0593 for <xml2rfc@ietfa.amsl.com>; Thu, 23 Apr 2020 15:41:56 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 yFXN_0iW5ZBZ for <xml2rfc@ietfa.amsl.com>; Thu, 23 Apr 2020 15:41:54 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 073523A047D for <xml2rfc@ietf.org>; Thu, 23 Apr 2020 15:41:53 -0700 (PDT)
Received: from [192.168.217.119] (p548DCD70.dip0.t-ipconnect.de [84.141.205.112]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 497XNc1DY4z10QX; Fri, 24 Apr 2020 00:41:52 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <0e83776e-831a-1b9a-2a96-7026c0b25ee8@htt-consult.com>
Date: Fri, 24 Apr 2020 00:41:51 +0200
Cc: Randy Bush <randy@psg.com>, XML2RFC Interest Group <xml2rfc@ietf.org>
X-Mao-Original-Outgoing-Id: 609374511.683951-50065397b45f7209583d711031504368
Content-Transfer-Encoding: quoted-printable
Message-Id: <00D455AE-A4DE-4C32-AC65-BFC8EE7CC9DF@tzi.org>
References: <m21roedm1p.wl-randy@psg.com> <0e83776e-831a-1b9a-2a96-7026c0b25ee8@htt-consult.com>
To: Robert Moskowitz <rgm@htt-consult.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/6Uh5qkVXyXSxJSdehvIu_TAyGa0>
Subject: Re: [xml2rfc] subsection failure
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <xml2rfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc/>
List-Post: <mailto:xml2rfc@ietf.org>
List-Help: <mailto:xml2rfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc>, <mailto:xml2rfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Apr 2020 22:41:56 -0000

On 2020-04-23, at 23:31, Robert Moskowitz <rgm@htt-consult.com> wrote:
> 
> My experience is that you cannot have text for a section after a subsection.
> 
> It all must go before the subsection or be in its own subsection.

Right.  This is pretty much a universal property of the section/subsection concept.
There is no way in standard typography to tell where a subsection ends without ending the entire section, except by starting another subsection on the same level.

So the (recursive) grammar is essentially:

section = t* section*

Where the t* is the introductory text for this section.

I don't think trying to innovate against centuries of the established practice for this is a useful exercise(*).

Grüße, Carsten

(*) In case of insurmountable urge to do so, you can always write a Python program.

v2.23.0 | Report a Bug | By Email