
From nobody Thu Aug 17 17:02:03 2017
Return-Path: <martin.thomson@gmail.com>
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 3D40C1326C2 for <xml2rfc-dev@ietfa.amsl.com>; Thu, 17 Aug 2017 17:02:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 O_epwXHbwLyd for <xml2rfc-dev@ietfa.amsl.com>; Thu, 17 Aug 2017 17:01:59 -0700 (PDT)
Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (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 B5F3E1326A8 for <xml2rfc-dev@ietf.org>; Thu, 17 Aug 2017 17:01:59 -0700 (PDT)
Received: by mail-it0-x234.google.com with SMTP id o72so3191860ita.0 for <xml2rfc-dev@ietf.org>; Thu, 17 Aug 2017 17:01:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=w05j5tZnfUMnQyYxkDw/+FsAsHBrpYmcOlxGlcHsWq8=; b=a7LqFwbLeQCvSmeq2uP4RRt0QAu91dszvM58yiC4Imoq1D8KkSmO4BpUzO8EXl1OJV sNb1vgSdE+WE+1lvwkbFoB7cjeLpnTDJ8aFBOXTPWefb0t4Y2JfGeb1HsMycTIWuBq3J mvAqagUAjBhfaRCl7s0SOF9uqyGsqvHB0Lo/2omy9zqPkWpWxsZii1NRycU4j//eeMZu 8n0vEjQqE6JkxlvJW4tkH0Lq8aq3o5PPxKOTZ2uPN3/4CrQfK74uGFyhnDYvsn+gf4Dn 6/rDF7smjEMVqBbRZjiHSW+R9IZ0aUrwbfffvf9KotkH557PGF9FwVD3U+L9jgO7R4+O X5aA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=w05j5tZnfUMnQyYxkDw/+FsAsHBrpYmcOlxGlcHsWq8=; b=hpDjIG0B7r8luVHW+agqLacInWKJm2R8grHh9fuMyCZy4sW+rYhUlSEq4UnLcmgdDR gnw7AcB/a7TuYKapEdui9p7Nle2e0TApIlK7q+AguNwBw60zRSZ3N2rY0W+pztyiMlxw qSSPEM1qByOFQMSCWzG46qdrT3+N+O6R5q78cetpEPG/Oq6RAPBfSAV8L6GKcxBAtd5D S8r5BEkI5RdGPWzXfn4S5CmkduX44vTjvMMztFIk4pGOMO8iru1Dz57DUYdFHP9oQQE0 Ctgeku1avSxPg7F5rRVc8XF6qu2f6BK67Mo1N3EuPC48g8yoLGVjE5DPs/L/5G5kZaNZ 6vtQ==
X-Gm-Message-State: AHYfb5hJAvw0u4u6WPS2cPmxecf0oSXQPifSDgZRAU+BetA5GPg1kzVs KK038DGMUWe0478NcDgtgYbyHaap6KyD9NE=
X-Received: by 10.36.120.16 with SMTP id p16mr126029itc.151.1503014518736; Thu, 17 Aug 2017 17:01:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.164.42 with HTTP; Thu, 17 Aug 2017 17:01:58 -0700 (PDT)
From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 18 Aug 2017 10:01:58 +1000
Message-ID: <CABkgnnWbOwTONJjfOAdYSRW2Vo5686OMq9zu5oTC5iRfcc4f1g@mail.gmail.com>
To: xml2rfc-dev@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/Lq_JHGpSalq45_WJLGiHgHgTl9M>
Subject: [xml2rfc-dev] Unwanted TOC in HTML rendering
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 18 Aug 2017 00:02:01 -0000

I don't often do this, but I wrote a draft that omits the TOC [1]

What I discover is that HTML versions get the TOC anyway.  It just
moves to the end of the document.  I'm undecided on whether I think
that this is a good idea or not, but I thought that I'd raise it.

[1] why no TOC is a default is somewhat perplexing.


From nobody Sat Aug 19 04:55:08 2017
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 9F0E91320CF for <xml2rfc-dev@ietfa.amsl.com>; Sat, 19 Aug 2017 04:55:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.899
X-Spam-Level: 
X-Spam-Status: No, score=-4.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, 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 HiSQet45ORcK for <xml2rfc-dev@ietfa.amsl.com>; Sat, 19 Aug 2017 04:55:05 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 87CDB1321EB for <xml2rfc-dev@ietf.org>; Sat, 19 Aug 2017 04:55:04 -0700 (PDT)
Received: from [172.16.100.221] ([14.207.74.127]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MVe87-1e4oUV3N55-00YyAw; Sat, 19 Aug 2017 13:55:01 +0200
To: Martin Thomson <martin.thomson@gmail.com>, xml2rfc-dev@ietf.org
References: <CABkgnnWbOwTONJjfOAdYSRW2Vo5686OMq9zu5oTC5iRfcc4f1g@mail.gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <1d373ec6-e936-89c3-ed38-d1be23409bf2@gmx.de>
Date: Sat, 19 Aug 2017 13:54:56 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CABkgnnWbOwTONJjfOAdYSRW2Vo5686OMq9zu5oTC5iRfcc4f1g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:I7E/Qwe39/OT8FUYNmQORqjPljibyIVlQr8rgKSV6KB6JCSVgyc H1b0CbLePIEvn817xznIL0fRmfISZvON/0p0so1FClRU3zdeN7JbqtTvTPqZH7jlleA2cZ1 IefmKjmR6fsFzdEi1wnXYqnKI0d710PuJ9AreTOa3eXGiLFB1DR8y6/tpd++mHQpsi6liUn O1sRZiByDMOtYCcWae/ug==
X-UI-Out-Filterresults: notjunk:1;V01:K0:LP3FkBb/QzA=:FyXxtI0EOyFehIQzm+EXVy VHoj5vmH5wUFoCK8aTQp9u+/DUOED+YormZ4GlJ1fQbZmW9kWUfiwE8uueBjwpxlsbleYLiyI cK3nwHG90bCbumFSJCcYh210Q3Uq07DOigRQGxlVL+J/GH/c3RVo7+RuC2sjAl5XorIfG7MEW 0JQxThC+DXHnTGlamEOUnl26De15xLRiiS363g49+0usco7s0VJOjodG/AeKZBfNiIr+Wwj/D PQ611F8Dna7ZcVCNVAVFMd7BlQliIjl03OsY2JATRPj5PKRrSNwt6qPOVn7QmZPIImtdOTm2q 4i/3Za4CV0IjYYUluGiArJnMx7wysgmvHlqHCmssYi01xudOixHZGOJQiJFauVY3pusBRt+n2 NY18J4pABzM84MtRNFMEMC28X10PUBFoZ1XZKf+CSC8fZoOFNn0MJtC/4Rsqrv7fXnv68TNFT 3HbYf3RWRJhwM8IRcOcpDrDzxPASK3ieiUHTDeV3dEWnkLnNpn18+ojahKiVzd7SBl/OXP4UI 9jUn6YrU3UP2Xr76MW6fLktsRvSY2vlsSHWAMZvoVQi/Jrf6XtcQnXLXVgGiwnGQ1B8uQV+N0 C3HS3XwjQQ0+4iNCPTzrq+3x8WfmikO/ICJOG0kN6WyhX4az/djPjHjNY5MovvVRd1wJdUTQM lDR084gn8Gqa8Tp5gnUWG68Ord5zHMc9brNSN1SIKrpRrxPZXo6EeON8FJJW2PUHrzXrORjcX jL53oTgWoswYo+YwDNpjvk6t9YfsV0sERWb/ZYexMIjmPPFK4AY3QDSHrJsag/BD5c6qv/7ml SvxHrif6DJZ1w1zru6NLsB4NeYKtYlsKk2mdFXevcfu9gJG/xw=
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/VS2e4Vz37ybF3Z7ko_fpV1vyAZE>
Subject: Re: [xml2rfc-dev] Unwanted TOC in HTML rendering
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 19 Aug 2017 11:55:07 -0000

On 2017-08-18 02:01, Martin Thomson wrote:
> ... > [1] why no TOC is a default is somewhat perplexing.

That changed in V3: 
<https://www.greenbytes.de/tech/webdav/rfc7991.html#element.rfc.attribute.tocInclude>

Best regards, Julian

