Re: [rfc-i] t with indent

Julian Reschke <julian.reschke@gmx.de> Wed, 30 December 2020 05:23 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC8963A0D42; Tue, 29 Dec 2020 21:23:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.2
X-Spam-Level:
X-Spam-Status: No, score=-2.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" 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 f-g51PGb26xA; Tue, 29 Dec 2020 21:23:06 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38B713A0D2D; Tue, 29 Dec 2020 21:23:06 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 620D1F406C6; Tue, 29 Dec 2020 21:22:36 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 7F57AF406C6 for <rfc-interest@rfc-editor.org>; Tue, 29 Dec 2020 21:22:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gmx.net
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lsSgtDukbe0v for <rfc-interest@rfc-editor.org>; Tue, 29 Dec 2020 21:22:31 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) by rfc-editor.org (Postfix) with ESMTPS id EACF7F40375 for <rfc-interest@rfc-editor.org>; Tue, 29 Dec 2020 21:22:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1609305777; bh=0MJoIUJXAQU/+qaOZaBIoNx7elkgnfUh11aTANdGg8Q=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=iuBo+RX83z89ePcNXWhQwiztBs2AswY7/4m5AN8h8w/EiU0tKwyf6y5f2HaI8+lzk APYUp3G47NFfvCfmLl1dpLUmNOOn4koQwLOUjIVTKnuLjCwgc/OwHCgS4sRbR2j2zT qcDv5dZKKE61MCPSaRsia9IL3ZiLHYzgYPDDqk3g=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [192.168.178.20] ([91.61.50.246]) by mail.gmx.com (mrgmx004 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MacOW-1kJlDn2Zru-00c5ZD for <rfc-interest@rfc-editor.org>; Wed, 30 Dec 2020 06:22:57 +0100
To: rfc-interest@rfc-editor.org
References: <CABcZeBOvxuD0pnWrkcywcKBMsd4CuCrLB4YkmDStpwh7e-SkSA@mail.gmail.com> <20201229204714.0FB903511F3C@ary.qy> <CABcZeBOQZBaiJ3vfSOL79bv60g1vR8+LCNNsYVg001EXPu+TSg@mail.gmail.com> <a7c58fc2-d342-12b6-8894-01599faef@taugh.com> <CABcZeBPLsY5BUj-msOZK-=uJigY=vb=UOCmw-jGFdzfS842sjw@mail.gmail.com> <6c76db91-6f75-ebb1-902d-53c43014f344@taugh.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <09ca06a1-0b9a-042f-d4f7-5d29fdf204e3@gmx.de>
Date: Wed, 30 Dec 2020 06:22:53 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <6c76db91-6f75-ebb1-902d-53c43014f344@taugh.com>
X-Provags-ID: V03:K1:ABCXvqHkBMeeO7XRymgKu+/eIOhhsZeKp4cjh+W0Hg9Y4+h2vqZ 1xnZAnTX9HY4p8C8pjitR4UR0lzG+B8xz6b3BjJyv48gfr+yjIuBL9AhDDIu7dnZBspxTsK //3aoNVTiSdlZLvzDeSSh1mbY7u8OmYYwDNiWPgdyhwJdlsroXRIXtMILuSmPGVMCYoSAyx LdSMTaLR9yf/b8GWqLSpQ==
X-UI-Out-Filterresults: notjunk:1;V03:K0:192JPERf4T8=:ehQIxse3jsyqMfMd7zZ/Md iwt31QX5O1durLJiVzZ8M7duOCRJHs5Zi8Q9EY4RcZtqiA0dqiBbgPwc+x/a3U4JN++yawGT+ /b981+a1eHu4uHnF5lqb58ZCvpXf6MoPOkXz7hBB6M6boY3vw3OyabqkS0ojVrx7OeNyey9qK WOyYZyB9itpdAs6+UwoDg4kKf4nG6VA/qmAejeQ1rVn2xfaRVYb43DNEn2Ta98RVUwawOAEWr GXum4R9rANfxHusnUgN2n2arw27noz3Ou9UZjBzrHXwVO/4V8eNjNQAypM4vFaTRA6yW/ZDWY tvmXkkE+5wEkmb4ssCtvVincamUAJFyCG0QqYQuoRBGmX5+wnGwRzn8VN7wa0YuxM+P9ec3EC JpIOv+SJloWkNdDyrAqDXajYFHrv4ow2iEwF9mUDY7MUZGIofDkKol/5oRfH0JXj5ZtZHx2Dk Lwd1MAeaQcpKcaPnXbq5RSM6RDzP7m7mA0VgbY3q3/HM1Q2LT/bSaao0+Nn/+zHjPb+c2bT1T 2S4pUnBqs8USVF07hbF198Vf27Qo4XEBlsNpiwGvcRPx1SOrL8SHbNm4jIL5188hd4BBtpUeU FVN0B+ODOeBfAwf/IeWuCkskethcJAGHY9uhW7HzLhFGkOdAuESSv5393VgOY/T/+05lSeZRE xQ7hqR0sjvDgwEiechBLhxXr3YP/rOO3KAjvyd+kqB4vuowOv31PLJWPUvr+6Zf90pZO53BNk IQ46pA+X4E04lZRqh+zWc+hwqkGIR01hSmycOoz6A6j6wQah9qYw+xiIgs0QLVFJ5BRM2smdM 2kZ7bvqpZ5LfvM9cqG6H81EEFReROKbm/9j/xivqRnBIrxkLFvP5Y8GxBtfrJ9fE6m1IGO5/8 l99oQWyYHzyZ24hJOuJg==
Subject: Re: [rfc-i] t with indent
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

Am 29.12.2020 um 23:47 schrieb John R Levine:
>> Do we have a list of the cases where this has happened? If so, I'd be
>> willing to sample and do a survey.
>
> This comes pretty close:
>
> $ egrep '<ul.*empty="true"' rfc8*.xml|egrep -v
> 'section-toc|section-boilerplate'
>
> There's also about 1500 empty tag lists used to indent TOC lines to
> follow section nesting with pn="section-toc-something".  I suppose
> that's one that could be replaced with a more complex <toc> tag.

Yes, but those should never have made it into the prepped XML. xml2rfc
inlines the generated ToC (and also expanded "authors" sections). This
is because it internally uses them in an intermediate step before
rendering (which is fine), but they never should leak into the canonical
XML and also not affect the user-visible XML grammar.

A bug (or if you want debatable design decision) leading to more confusion.

Best regards, Julian
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest