Re: [xml2rfc] subsection failure

Randy Bush <randy@psg.com> Thu, 23 April 2020 21:49 UTC

Return-Path: <randy@psg.com>
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 4354E3A1439 for <xml2rfc@ietfa.amsl.com>; Thu, 23 Apr 2020 14:49:59 -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 On5GrCW5FQnH for <xml2rfc@ietfa.amsl.com>; Thu, 23 Apr 2020 14:49:57 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (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 BF0CB3A1438 for <xml2rfc@ietf.org>; Thu, 23 Apr 2020 14:49:57 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.rg.net) by ran.psg.com with esmtp (Exim 4.90_1) (envelope-from <randy@psg.com>) id 1jRjjI-0004QD-Q0; Thu, 23 Apr 2020 21:49:56 +0000
Date: Thu, 23 Apr 2020 14:49:56 -0700
Message-ID: <m2mu71dg8r.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Robert Moskowitz <rgm@htt-consult.com>
Cc: XML2RFC Interest Group <xml2rfc@ietf.org>
In-Reply-To: <8784b823-b1eb-1920-0a89-f6e28d0966db@htt-consult.com>
References: <m21roedm1p.wl-randy@psg.com> <0e83776e-831a-1b9a-2a96-7026c0b25ee8@htt-consult.com> <m2pnbxdgwh.wl-randy@psg.com> <8784b823-b1eb-1920-0a89-f6e28d0966db@htt-consult.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/26.3 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/0wTpXGaj1LmJpDzdkUbh1YMxyh8>
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 21:49:59 -0000

>>> It all must go before the subsection or be in its own subsection.
>> yikes!
> 
> that was my feeling when I figured out i had to think about writing as:
> 
> 2.
> 
> stuff
> 
> 2.1
> 
>    more stuff
> 
> 2.2
> 
>   more stuff

does not work when 2 is the introduction, as it is in this case

> But I can kind of see it.  In that how can the reader, necessarily see
> that 2.2 above ended and the following text is back to 2?

indentation?  yes, i know.

randy