Re: [Rfc-markdown] RfcMarkup ToC has no links

Anders Rundgren <anders.rundgren.net@gmail.com> Mon, 01 June 2020 12:26 UTC

Return-Path: <anders.rundgren.net@gmail.com>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFB413A0FE5; Mon, 1 Jun 2020 05:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 O0N3ZhOtozK3; Mon, 1 Jun 2020 05:26:42 -0700 (PDT)
Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (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 3A5DC3A0F5F; Mon, 1 Jun 2020 05:26:42 -0700 (PDT)
Received: by mail-wr1-x434.google.com with SMTP id j10so11277477wrw.8; Mon, 01 Jun 2020 05:26:42 -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=NNbqdQoDDHZga+DJlWbarOKVWvZY5WmGmPyEfEeWDXY=; b=NV+SUN6XjRSuZn1NZ4REgy7LNC/s5m4YbpAXtvhNxsH5q0YYs0YjkvQQRlN9c8caZp l98llrDPjTOK0HSG1Ybl7DzL2VYuzM2QXuAuI6g/82yMUL5qkOBYopJzfLCuKqULaKCW 7PnYOLcpPLz05vxAi+2GmrsvaFUU2OwxmWdlymzZuyYieQBBG9TnvQMNp+9QmW/rkwec pWdi+m9/ZvUnqY7dUcy1uqQIaAvsrVzgqLSbHBmwJ51pJfIZqorDRMzR+Y7FUbri8wcX e5WzcfMphvXFewARKSmhxO04Zzuqv+PI0gUQUWPpi8Mf1aAMRYZhGtGJ8dn8xSQZ6CTS lNaA==
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=NNbqdQoDDHZga+DJlWbarOKVWvZY5WmGmPyEfEeWDXY=; b=ATxLiotelevDGU+QFc9hh61X67aznFwAZcFBuAjmR7OIxNvwLwLsew7+TAzHsY012W WLzAd4+ZGPHR4adbkcROutWWEt/0egtkJWs5S76r2RiWVb0vjGrcNkl/nhYhPwSfgxP8 lAwHg3IA7eztt5GZjgIXzFznu+gVwyt61P96CY/ws2bPtriOG65ZhFCbRwOqZzrniu0a EvXJG9vqUm7w2LzV3rqVxImNabA2t+L242cWZ+Dd69XugDRnNnZSZoDhSvqTI/LkOerm SJqJr8gysSfO0kPnlrPrdBTjdQ1cgOjV3zOu/q7gFoElgn7Mlxau3BuCN31eYwUKsSIY LFDQ==
X-Gm-Message-State: AOAM532kvsWkbXn/gPlsZwxA1dfOuzqn5zMbcaSfFs7DI8dg3ieA1rnB X7cBvBTLHuJu5/GjEIM2FhEiAKm3T10=
X-Google-Smtp-Source: ABdhPJw/MpJpd25wjFD4QQSwaWqkGxXHfESsMCVVxPidmRnuSH2KT82CQvw9AaH8R+Gs5fIK8Wk11g==
X-Received: by 2002:a5d:6a03:: with SMTP id m3mr21568173wru.293.1591014400226; Mon, 01 Jun 2020 05:26:40 -0700 (PDT)
Received: from [192.168.1.79] (25.131.146.77.rev.sfr.net. [77.146.131.25]) by smtp.googlemail.com with ESMTPSA id s7sm20595931wrr.60.2020.06.01.05.26.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 01 Jun 2020 05:26:39 -0700 (PDT)
To: Henrik Levkowetz <henrik@levkowetz.com>, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
References: <E1iNIwd-0006wR-VI@durif.tools.ietf.org> <abda3104-191c-8ca3-c254-64ed55ccd9dd@gmail.com> <481b0289-f3d0-f10a-32d6-1b6f6f84a6f2@levkowetz.com>
From: Anders Rundgren <anders.rundgren.net@gmail.com>
Message-ID: <1cb7df0c-38fd-3e76-abfc-34ed84c34c1a@gmail.com>
Date: Mon, 1 Jun 2020 14:26:38 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.8.1
MIME-Version: 1.0
In-Reply-To: <481b0289-f3d0-f10a-32d6-1b6f6f84a6f2@levkowetz.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/wDG1rfiRh-imlN1xCeP67qxqTEg>
Subject: Re: [Rfc-markdown] RfcMarkup ToC has no links
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jun 2020 12:26:44 -0000

On 2020-06-01 14:00, Henrik Levkowetz wrote:
> Hi Anders,

Hi Henrik,

I understand (technically) why you ended up with this after removing pagination but for those who write documents it surely looks like a bug.

The quick (and right?) fix would be to update the publishing system with a "deprecated" note for RfcMarkup.

If RfcMarkup is not deprecated I have a feeling we need a common plain-text/RfcMarkup generator.  The RfcMarkup system always had strange quirks with respect to links and after your explanation I finally understand why :)

Regards,
Anders

> 
> On 2020-05-30 04:43, Anders Rundgren wrote:
>> sample RFC: https://tools.ietf.org/html/rfc8759
>>
>> That the page number links are gone is understandable since there
>> (fortunately) is no paging anymore but removing links for headers
>> seem illogical in an HTML formatted document.
>>
>> I understand that the IETF want to retire the RfcMarkup format but
>> since the IETF apparently still publish in this format, shouldn't
>> also stay useful?
> 
> The rfcmarkup generated documents are generated from the plain text
> documents published by the RFC Editor, not directly from XML.  As
> such, there are a lot of heuristics involved in recognizing different
> parts of the document for what they are.  In particular, the spaced
> dots (periods) which are part of the ToC, are used to recognize the
> entries as ToC entries, rather than section titles.
> 
> So rendering without pages and page numbers has the effect of depriving
> the htmlizer of the cues it needs to generate links from the ToC.
> 
>> I'm currently in the auth48 state and the on-line xml2rfc tool
>> produces ToC links for appendices(!).  Is that a bug or a feature?
> 
> Feature.
> 
> 
> 	Henrik
>