Re: [rfc-i] [irsg] Resending: Page numbers in RFCs questions / preferences

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 27 October 2020 05:11 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 2CFC33A1585; Mon, 26 Oct 2020 22:11:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.445
X-Spam-Level:
X-Spam-Status: No, score=-2.445 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, 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.247, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (body has been altered)" 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 0Rqnzo4BcLIX; Mon, 26 Oct 2020 22:11:39 -0700 (PDT)
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 C98803A1582; Mon, 26 Oct 2020 22:11:39 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B5C0AF407AD; Mon, 26 Oct 2020 22:11:28 -0700 (PDT)
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 9C613F407AD for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 22:11:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 TyrUpz1DRnHN for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 22:11:22 -0700 (PDT)
Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) by rfc-editor.org (Postfix) with ESMTPS id 23239F407A7 for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 22:11:22 -0700 (PDT)
Received: by mail-pg1-x532.google.com with SMTP id r10so87698pgb.10 for <rfc-interest@rfc-editor.org>; Mon, 26 Oct 2020 22:11:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=9nLvL4xl/37bp9ifw8MbuKeJDU3Rk+YOJtYr9MtCAoE=; b=Abj/ldbJbFm48OBghP/4BbbX9I0cWCbzVVD6b0zPGp6IozWPP11y6h95Y0FQX+q/VO EWvtIoxabAJH4Bsjv30mPXEfUaq8TidGr41yPrNiJiEqUUD/2DF1BVMXvZIFkD7DL1jK A3wYHCBYT5NTrcEOhBuC+iMyIBtuXk0R+aMjXmMo1HXbvNfOGWuDB+9JJ8sLUSsdKdwl rZks1VqHQ7/YjH14vLfGrEGEs2FTwbq01hXbIynaHPCFUoQFRnt8sHHodTrQsjGk9E5Q etR2Zak/kUSLeij0qQ/FEHPZr3F/cON9LV9nB5JSzXphrX66C/G+8kgOwYD7B+pL8Mag CmmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=9nLvL4xl/37bp9ifw8MbuKeJDU3Rk+YOJtYr9MtCAoE=; b=LjNs+Q09JXkf6+E9fdMIVYVkrQ4Bk/SQ6PWxf4ILHeu2qx+/ZW2uSb6O5mg8EpWvaQ HJz7MIaODB5JHC2bbWjIXipN+c5rBd140hQvOIdarLEUtfiFLf6KREjBbxXrRoZdu9fK 8PCQgrHqy27HSb9jZ07YV2BDh7d3h6aVzBR7Sp9h0lvruGHVAmHbaMrILqXGw81CP/uC vIKoJlaoMKfoq0iczosTS+vi14ebqajSDJ+rjLRGArXVyA47ZQcphYsw01bI3RtWt/ej Af1OlsMXyZcybMi+ntAuFwCfYasdrBdJ+Z6Zr9/2BdS3CfxgOUfErY5nZuasacH+4ZIg h3fg==
X-Gm-Message-State: AOAM533CQlQCt3IJXdyUWgvQqmMdHJaflXxYR4RKlp9r6GcGhpcvdoid y+zlaYSaO8KOvq/9szxbcjsSja2I/Io=
X-Google-Smtp-Source: ABdhPJzRzAA/V83DJfyrTiaFhRxZkwCOJK4GT9dR98LR18GtBs2ogNxv0F/ZjsCmWNr3U+KXTNbOHw==
X-Received: by 2002:a63:29c8:: with SMTP id p191mr400601pgp.241.1603775490515; Mon, 26 Oct 2020 22:11:30 -0700 (PDT)
Received: from [192.168.178.20] ([151.210.130.0]) by smtp.gmail.com with ESMTPSA id mm19sm451800pjb.45.2020.10.26.22.11.27 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Oct 2020 22:11:29 -0700 (PDT)
To: Benjamin Kaduk <kaduk@mit.edu>, John Levine <johnl@taugh.com>
References: <20201026215117.GY39170@kduck.mit.edu> <20201026222427.8D3B624F19C4@ary.qy> <20201026235341.GA39170@kduck.mit.edu>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <47e062c3-0f1f-02fd-d77f-645863af93aa@gmail.com>
Date: Tue, 27 Oct 2020 18:11:25 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <20201026235341.GA39170@kduck.mit.edu>
Content-Language: en-US
Subject: Re: [rfc-i] [irsg] Resending: Page numbers in RFCs questions / preferences
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>
Cc: rfc-interest@rfc-editor.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 27-Oct-20 12:53, Benjamin Kaduk wrote:
> On Mon, Oct 26, 2020 at 06:24:27PM -0400, John Levine wrote:
>> In article <20201026215117.GY39170@kduck.mit.edu> you write:
>>>> For individual sections, the TOC absolutely should provide linkage to
>>>> sections, especially in formats like HTML.
>>>
>>> The native HTML format does.  I have no idea why the htmlization script
>>> can't or does not do so for new-format RFCs.
>>
>> There is no htmlization script for new-format RFCs. The HTML format is
>> produced directly from the XML and has all the links you'd expect, as
>> does the PDF. The text format loses a lot of info visible in the other
>> formats so it is a third-best option.
>>
>> I suppose you could render to text and try to htmlize that but it's
>> hard to imagine a reason to do so.
> 
> I don't know what https://tools.ietf.org/html/rfc8815 is (conveniently
> linked from https://datatracker.ietf.org/doc/rfc8815/ as "htmlized") if not
> trying to htmlize the text copy.  I am well aware that the new format
> produces direct ("native") HTML output, and indeed was attempting to point
> Jeff towards the native HTML output.

Right. I think we should debate whether it's a good or a bad idea to run
the htmlization script on v3 format documents. I'd say "bad" because all
it does is create confusion.

Running rfcdiff on the plain text version is very useful, however.

    Brian
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest