Re: [xml2rfc] subsection failure

Robert Moskowitz <rgm@htt-consult.com> Thu, 23 April 2020 22:04 UTC

Return-Path: <rgm@htt-consult.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 0DE033A0A99 for <xml2rfc@ietfa.amsl.com>; Thu, 23 Apr 2020 15:04:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level:
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 eL0jFsW75yNM for <xml2rfc@ietfa.amsl.com>; Thu, 23 Apr 2020 15:04:37 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (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 1AA903A146A for <xml2rfc@ietf.org>; Thu, 23 Apr 2020 15:04:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 6A9B262271; Thu, 23 Apr 2020 18:04:29 -0400 (EDT)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id OQELGAgDAHPr; Thu, 23 Apr 2020 18:04:26 -0400 (EDT)
Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 18A3E6216A; Thu, 23 Apr 2020 18:04:25 -0400 (EDT)
To: Randy Bush <randy@psg.com>
Cc: XML2RFC Interest Group <xml2rfc@ietf.org>
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> <m2mu71dg8r.wl-randy@psg.com>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <307d1dad-6e3b-2f86-3383-04b76eeee161@htt-consult.com>
Date: Thu, 23 Apr 2020 18:04:19 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <m2mu71dg8r.wl-randy@psg.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/TwAl1xigoVEu64EZVw_EkoKEOv4>
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:04:43 -0000


On 4/23/20 5:49 PM, Randy Bush wrote:
>>>> 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

Change all my 2. to 1. and the same is true.

>
>> 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.

We do not indent subsections.  Not our style.   ;)

In fact I have seen subsections 6 deep.  Think about how little space 
would be left for text with the extent of the left white space!

>
> randy