Re: [xml2rfc] can xref section= reference an anchor?
Robert Moskowitz <rgm@htt-consult.com> Mon, 16 December 2019 17:30 UTC
Return-Path: <rgm@htt-consult.com>
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 D2423120881 for <xml2rfc@ietfa.amsl.com>; Mon, 16 Dec 2019 09:30:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 xO1d6XeRHTmX for <xml2rfc@ietfa.amsl.com>; Mon, 16 Dec 2019 09:30:24 -0800 (PST)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0E44120875 for <xml2rfc@ietf.org>; Mon, 16 Dec 2019 09:30:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id 10AC16212F; Mon, 16 Dec 2019 12:30:23 -0500 (EST)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id y-2s+PBGV+-c; Mon, 16 Dec 2019 12:30:17 -0500 (EST)
Received: from lx140e.htt-consult.com (unknown [192.168.160.12]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id 05B226212E; Mon, 16 Dec 2019 12:30:16 -0500 (EST)
To: Julian Reschke <julian.reschke@gmx.de>, "xml2rfc@ietf.org" <xml2rfc@ietf.org>
References: <5d192de5-c6ca-aa1f-b7e0-0500704e491a@htt-consult.com> <13eeba5e-bb17-a0dc-cf21-8380150f480d@gmx.de> <2e3a4d01-34e2-5609-5179-3ddd47493947@htt-consult.com> <9193046f-22f1-e9f2-0a11-86d622ab11fd@gmx.de>
From: Robert Moskowitz <rgm@htt-consult.com>
Message-ID: <83e5ec0e-4182-5a75-c312-aaa238a98985@htt-consult.com>
Date: Mon, 16 Dec 2019 12:30:11 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <9193046f-22f1-e9f2-0a11-86d622ab11fd@gmx.de>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc/7jrZPJtpUSC6zNTUgCdB-0Zy_Zo>
Subject: Re: [xml2rfc] can xref section= reference an anchor?
X-BeenThere: xml2rfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Mon, 16 Dec 2019 17:30:26 -0000
On 12/16/19 12:18 PM, Julian Reschke wrote: > On 16.12.2019 18:07, Robert Moskowitz wrote: >> >> >> On 12/16/19 12:01 PM, Julian Reschke wrote: >>> On 16.12.2019 17:47, Robert Moskowitz wrote: >>>> I see examples of section=5 for RFCs, but for IDs, the section number >>>> will tend to be version specific. >>>> >>>> Is there a way to reference the anchor label for the desired section? >>>> >>>> I am missing it in the FAQs. >>> >>> You set anchor="label" on the section that you want to reference, and >>> then use <xref target="label"/> in order to reference it. >> >> I was not clear enough. >> >> Consider: >> >> <xref target="I-D.moskowitz-orchid-cshake" format="default" >> section="4" sectionFormat="of">"Using cSHAKE in ORCHIDs"</xref> >> >> And in moskowitz-orchid-cshake I have: >> >> <section anchor="Decode" numbered="true" toc="default"> <name>ORCHID >> Decoding</name> >> >> I want to use that anchor, "Decode" from the xml, not the section # that >> ended up in the current ver of the draft's txt. >> ... > > That's not currently possible in xml2rfc. > > It *is* possible, if you run a preprocessor on the XML (such as the one > coming with rfc2629.xslt, but that in turn currently only supports a > subset of v3). I kind of thought this would be the case. You basically have to run xml2rfc to get the section # assigned to the section. I remember times past struggling to kept all the sec # aligned in a set of cross-referenced drafts. So put this into a feature request :)
- [xml2rfc] can xref section= reference an anchor? Robert Moskowitz
- Re: [xml2rfc] can xref section= reference an anch… Julian Reschke
- Re: [xml2rfc] can xref section= reference an anch… Paul Kyzivat
- Re: [xml2rfc] can xref section= reference an anch… Robert Moskowitz
- Re: [xml2rfc] can xref section= reference an anch… Julian Reschke
- Re: [xml2rfc] can xref section= reference an anch… Robert Moskowitz
- Re: [xml2rfc] can xref section= reference an anch… Julian Reschke
- Re: [xml2rfc] can xref section= reference an anch… Carsten Bormann
- Re: [xml2rfc] can xref section= reference an anch… Julian Reschke
- Re: [xml2rfc] can xref section= reference an anch… Paul Kyzivat
- Re: [xml2rfc] can xref section= reference an anch… Robert Moskowitz
- Re: [xml2rfc] can xref section= reference an anch… Julian Reschke
- Re: [xml2rfc] can xref section= reference an anch… Paul Kyzivat
- Re: [xml2rfc] can xref section= reference an anch… Julian Reschke
- Re: [xml2rfc] can xref section= reference an anch… Carsten Bormann
- Re: [xml2rfc] can xref section= reference an anch… Julian Reschke
- Re: [xml2rfc] can xref section= reference an anch… Julian Reschke