[xml2rfc-dev] rfc2629 xslt question
Tom Pusateri <pusateri@bangj.com> Thu, 07 March 2019 02:45 UTC
Return-Path: <pusateri@bangj.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 523B4131348 for <xml2rfc-dev@ietfa.amsl.com>; Wed, 6 Mar 2019 18:45:42 -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, 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 4FaaIsj4yVxc for <xml2rfc-dev@ietfa.amsl.com>; Wed, 6 Mar 2019 18:45:39 -0800 (PST)
Received: from oj.bangj.com (69-77-154-174.static.skybest.com [69.77.154.174]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54AA213131E for <xml2rfc-dev@ietf.org>; Wed, 6 Mar 2019 18:45:39 -0800 (PST)
Received: from [172.16.10.104] (mta-107-13-246-59.nc.rr.com [107.13.246.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by oj.bangj.com (Postfix) with ESMTPSA id 3C0F729565 for <xml2rfc-dev@ietf.org>; Wed, 6 Mar 2019 21:45:38 -0500 (EST)
From: Tom Pusateri <pusateri@bangj.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Message-Id: <846D0EFD-ADFE-427B-A8C7-5A71FEB7CA7B@bangj.com>
Date: Wed, 06 Mar 2019 21:45:37 -0500
To: xml2rfc-dev@ietf.org
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/jYAZnImNBbfgzMHEwrdt9hFBK5k>
Subject: [xml2rfc-dev] rfc2629 xslt question
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 07 Mar 2019 02:45:42 -0000
When using markdown-rfc2629 to generate XML and rfc2629.xslt and friends to create a standalone XML file, I notice that my Appendix A Section gets a header of just A. Meanwhile, the TXT and HTML versions generated by XML2RFC get a header of Appendix A. You can see it here online: https://tools.ietf.org/id/draft-pusateri-dnssd-update-proxy-01.xml (Scroll to the end) and after grabbing the latest versions from greenbytes.de, the same thing happens locally. Is this intentional or just an oversight? Thanks, Tom
- [xml2rfc-dev] rfc2629 xslt question Tom Pusateri
- Re: [xml2rfc-dev] rfc2629 xslt question Julian Reschke
- Re: [xml2rfc-dev] rfc2629 xslt question Julian Reschke
- Re: [xml2rfc-dev] rfc2629 xslt question Tom Pusateri
- Re: [xml2rfc-dev] rfc2629 xslt question Tom Pusateri
- Re: [xml2rfc-dev] rfc2629 xslt question Julian Reschke