Browse Prior Art Database

Writing I-Ds and RFCs Using Pandoc and a Bit of XML (RFC7328)

IP.com Disclosure Number: IPCOM000238264D
Original Publication Date: 2014-Aug-01
Included in the Prior Art Database: 2014-Aug-13
Document File: 20 page(s) / 18K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Gieben: AUTHOR

Abstract

This document presents a technique for using a Markdown [Markdown] syntax variant, called Pandoc [Pandoc], and a bit of XML [RFC2629] as a source format for documents that are Internet-Drafts (I-Ds) or RFCs.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 15% of the total text.

Independent Submission                                         R. Gieben Request for Comments: 7328                                        Google Category: Informational                                      August 2014 ISSN: 2070-1721

           Writing I-Ds and RFCs Using Pandoc and a Bit of XML

Abstract

   This document presents a technique for using a Markdown syntax    variant, called Pandoc, and a bit of XML (as defined in RFC 2629) as    a source format for documents that are Internet-Drafts (I-Ds) or    RFCs.

   The goal of this technique (which is called Pandoc2rfc) is to let an    author of an I-D focus on the main body of text without being    distracted too much by XML tags; however, it does not alleviate the    need to typeset some files in XML.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This is a contribution to the RFC Series, independently of any other    RFC stream.  The RFC Editor has chosen to publish this document at    its discretion and makes no statement about its value for    implementation or deployment.  Documents approved for publication by    the RFC Editor are not a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7328.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.

 Gieben                        Informational                     [Page 1]
 RFC 7328                       Pandoc2rfc                    August 2014

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2

   2.  Pandoc to RFC . . . . . . . . . . . . . . . . . . . . . . . .   2

     2.1.  Dependencies  . . . . . . . . . . . . . . . . . . . . . .   5

   3.  Building an Internet-Draft  . . . . . . . . . . . . . . . . .   5

   4.  Supported Features  . . . . . . . . . . . . . . . . . . . . .   5

   5.  Unsupported Features and Limitations  . . . . . . . . . . . .   7

   6.  Pandoc Style  . . . . . . . . . . . . . . . . . . . . . . . .   7

     6.1.  Figures . . . . . . . . . . . . . . . . . . . . . . . . .  ...