IETF Logo Mail Archive

Re: [xml2rfc] help request: suggestions for reconstructing the Tao ToC for use in RFC

Kesara Rathnayake <kesara@staff.ietf.org> Thu, 11 January 2024 21:48 UTC

Return-Path: <kesara@staff.ietf.org>
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 1AB8FC14F6A3 for <xml2rfc@ietfa.amsl.com>; Thu, 11 Jan 2024 13:48:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=staff-ietf-org.20230601.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VhzEMr_MCcoo for <xml2rfc@ietfa.amsl.com>; Thu, 11 Jan 2024 13:48:09 -0800 (PST)
Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com [IPv6:2a00:1450:4864:20::629]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC557C14F697 for <xml2rfc@ietf.org>; Thu, 11 Jan 2024 13:48:09 -0800 (PST)
Received: by mail-ej1-x629.google.com with SMTP id a640c23a62f3a-a2c375d2430so176557166b.1 for <xml2rfc@ietf.org>; Thu, 11 Jan 2024 13:48:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1705009687; x=1705614487; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=PJqm8pfBGZJPAbdFq04OQVYKNE1o8zwRvATKkgXPTFM=; b=MSbtrnZwSumi2WjlPGjUeLMJCt4gNB0rXgLnPPXZD2nO4UdfQ/pl1dQYgaZGXNIKuR 003zixe5HIQzpJUQis+IMHCJlmlmTL/IWjvj4s6+U7DNNTIIKO4coKjPLKqNgAOrrpcc xH5sq7wVe/IDuATRkUIY7slNYbvxjaYor3f7ead3YoqvzC7nblAKxW5spaE3wZzeJUs7 xT8BB52ozCzAAJNlWHAkjhHEBT0vXh+GSuDhXRvcFAr3nCPic+VKA/XN8SA6PZM+W28p IZ7O+I2bWjnhk+3boKtnp4R1xQxNXjoeXF8NN6pfUsh/L0SOjuKHtrbUti2qtUVG0+hU GDsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705009687; x=1705614487; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=PJqm8pfBGZJPAbdFq04OQVYKNE1o8zwRvATKkgXPTFM=; b=EwjGAaOS5l05LA9fpM7g4M3g0Nhr0a8jzkWiDnX0nFPYvcw4xcMhu8KAI/Wsjlqbc4 btHw0LwXiYlkx2xuudy6F8AkP8K4nYS+ntPv9FMaP4KmurariGNCa34UqjU9JNyJvSVu WamxURFfnCLLQTcTOgdZaWdP9v0aixP2QQyc3ucMbFQoe/ASmv3mPza5FFTf36ln87Mu 5UlEQiSNPp7P35Mppb9x1KJyWpgtfdJ07ggQCX5Bhj46MagYX1NuAq5OG9Ufj5q03vMa 08tBKGzxaZinLrptvoG0024jQ6xGOknrSHB0Si8iAZVJ2srb+Nqbfx30s81v9VxJBjoH SnVQ==
X-Gm-Message-State: AOJu0Yzk/WKBOXTm9U4wqtZIkShXXgQwH4uKKelgYocnfhxswVPMpWm4 sPVCuXG78iCj6nPbvlkNChn6nBDz/RSM3nd6H5bhh8AvfnFHaEnnlAzQYi0doxY99w==
X-Google-Smtp-Source: AGHT+IExPXJWI/vwodQJPk7wanhCNW7AKnPEjVOcASORxTYTIPcobYwVmwWOLQ7xB6gDfYjnlUcj2UuguZy5iFB9/pg=
X-Received: by 2002:a17:906:6d12:b0:a2b:f9f7:2b79 with SMTP id m18-20020a1709066d1200b00a2bf9f72b79mr144797ejr.99.1705009687392; Thu, 11 Jan 2024 13:48:07 -0800 (PST)
MIME-Version: 1.0
References: <8b646de5-2609-4127-bc8f-ea285231135a@nielstenoever.net> <a92572b5-c07e-467d-8474-26f0d758e4b0@nielstenoever.net> <CAD2=Z86a3dDzv9Qi7Dv==UuhQNfxuK0bpdUjHDaXNUwtLX6=XA@mail.gmail.com> <6ff20dd5-7293-4178-bb07-5624a22a4186@nielstenoever.net>
In-Reply-To: <6ff20dd5-7293-4178-bb07-5624a22a4186@nielstenoever.net>
From: Kesara Rathnayake <kesara@staff.ietf.org>
Date: Fri, 12 Jan 2024 10:47:55 +1300
Message-ID: <CAD2=Z878H_1v39EZVD-tsy6Z+86rwzbPi4dZjAs1X=-+F6ZEuA@mail.gmail.com>
To: Niels ten Oever <mail@nielstenoever.net>
Cc: xml2rfc@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/cPC5a8lU5-mK30T88EVGsB-8eBs>
Subject: Re: [xml2rfc] help request: suggestions for reconstructing the Tao ToC for use in RFC
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: XML2RFC discussion list <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, 11 Jan 2024 21:48:14 -0000

On Fri, 12 Jan 2024 at 10:21, Niels ten Oever <mail@nielstenoever.net> wrote:
>
> Thanks a lot Kesara,
>
> The problem is that we need a ToC _only for the annex_ (which is the last archival version), not the whole document.
>
> Any suggestions how we could do that?
>

I think this has to be done in the prepped version of the XML.
So start with markdown without a ToC,
kramdown-rfc draft-retirement.md > draft-retirement.xml
xml2rfc --preptool draft-retirement.xml # generate prepped document
# make ToC changes in draft-retirement.prepped.xml
xml2rfc --text --html draft-retirement.prepped.xml

  --Kesara

> Best,
>
> Niels
>
> On 11-01-2024 22:18, Kesara Rathnayake wrote:
> > Hi Niels,
> >
> > Regarding errors with ToC, remove the ToC from markdown file.
> > xml2rfc automatically generates the ToC for you.
> >
> > Cheers,
> > Kesara
> >
> > On Fri, 12 Jan 2024 at 08:22, Niels ten Oever <mail@nielstenoever.net> wrote:
> >>
> >> Hi all,
> >>
> >> I am at a bit of a loss here and would appreciate some guidance.
> >>
> >> Greg Wood and I have been working on reverting the html tags that make the ToC work in the current web-version of the Tao, to a ToC that would work in an RFC, but only at the end of an RFC, because we want to create an archival version of the Tao as an annex to a possible Tao tombstone draft.
> >> But we are a bit at a loss as how to create a working ToC of the headings in the archival version of the Tao?
> >>
> >> We are currently working in this document: https://github.com/ietf/tao/blob/main/draft-retirement.md
> >>
> >> I am getting a lot of complaints from xml2rfc that <vspace/> is removed, but I am not sure what to replace it with?
> >>
> >> All suggestions are very much welcomed!
> >>
> >> Thanks in advance,
> >>
> >> Niels
> >>
> >>
> >>
> >>
> >> --
> >> Niels ten Oever, PhD
> >> Co-Principal Investigator - critical infrastructure lab - University of Amsterdam
> >> Assistant Professor - Department of European Studies - University of Amsterdam
> >>
> >> W: https://criticalinfralab.net
> >> W: https://nielstenoever.net
> >> PGP: 4254 ECD5 D4CF F6AF 8B91 0D9F EFAD 2E49 CC90 C10C
> >> _______________________________________________
> >> xml2rfc mailing list
> >> xml2rfc@ietf.org
> >> https://www.ietf.org/mailman/listinfo/xml2rfc
> >
> >
> >
>
> --
> Niels ten Oever, PhD
> Co-Principal Investigator - critical infrastructure lab - University of Amsterdam
> Assistant Professor - Department of European Studies - University of Amsterdam
>
> W: https://criticalinfralab.net
> W: https://nielstenoever.net
> PGP: 4254 ECD5 D4CF F6AF 8B91 0D9F EFAD 2E49 CC90 C10C



-- 
Kesara Rathnayake
Senior Software Development Engineer - IETF Administration LLC
kesara@staff.ietf.org

v2.23.0 | Report a Bug | By Email