Software:Pandoc

From HandWiki
Short description: Software for converting between text document formats
Pandoc
Original author(s)John MacFarlane
Initial release10 August 2006 (17 years ago) (2006-08-10)
Written inHaskell
Operating systemUnix-like, Windows
PlatformCross-platform
LicenseGNU GPLv2
Websitepandoc.org

Pandoc is a free-software document converter, widely used as a writing tool (especially by scholars)[1] and as a basis for publishing workflows.[2] It was created by John MacFarlane, a philosophy professor at the University of California, Berkeley.[3]

Functionality

Pandoc dubs itself a "markup format" converter. It can take a document in one of the supported formats and convert only its markup to another format. Maintaining the look and feel of the document is not a priority.[4]

Plug-ins for custom formats can also be written in Lua, which has been used to create an exporting tool for the Journal Article Tag Suite, for example.[5]

CiteProc

An included CiteProc option allows pandoc to use bibliographic data from reference management software in any of five formats: BibTeX, BibLaTeX, CSL JSON or CSL YAML, or RIS.[6] The information is automatically transformed into a citation in various styles (such as APA, Chicago, or MLA) using an implementation of the Citation Style Language.[6] This allows the program to serve as a simpler alternative to LaTeX for producing academic writing in Markdown with inline citation keys.[7] Or the program can be used to convert any bibliographic data stream in the accepted formats into a list of citations in a chosen style.[8]

Supported file formats

Input formats

The input format with the most support is an extended version of Markdown.[9] Notwithstanding, pandoc can also read in the following formats:

Output formats

Pandoc can create files in the following output formats, which are not necessarily the same set of formats as the input formats:

See also

References

  1. Mullen, Lincoln (23 February 2012). "Pandoc Converts All Your (Text) Documents". The Chronicle of Higher Education Blogs: ProfHacker. http://chronicle.com/blogs/profhacker/pandoc-converts-all-your-text-documents/38700. 
    - McDaniel, W. Caleb (28 September 2012). "Why (and How) I Wrote My Academic Book in Plain Text". W. Caleb McDaniel at Rice University. http://wcm1.web.rice.edu/my-academic-book-in-plain-text.html. 
    - Healy, Kieran (23 January 2014). "Plain Text, Papers, Pandoc". http://kieranhealy.org/blog/archives/2014/01/23/plain-text/. 
    - Ovadia, Steven (2014). "Markdown for Librarians and Academics". Behavioral & Social Sciences Librarian 33 (2): 120–124. doi:10.1080/01639269.2014.904696. ISSN 0163-9269. http://academicworks.cuny.edu/lg_pubs/7/. 
  2. Till, Kaitlyn; Simas, Shed; Larkai, Velma (14 April 2014). "The Flying Narwhal: Small mag workflow". Publishing @ SFU. http://tkbr.publishing.sfu.ca/mpub/2014/04/14/the-flying-narwhal-small-mag-workflow/#more-639. 
    - Maxwell, John (1 November 2013). "Building Publishing Workflows with Pandoc and Git". Publishing @ SFU. http://www.ccsp.sfu.ca/2013/11/building-publishing-workflows-with-pandoc-and-git/. 
    - Maxwell, John (26 February 2014). "On Pandoc". eBound Canada: Digital Production Workshop, Vancouver, BC. http://tkbr.ccsp.sfu.ca:5001/Slides/On%20Pandoc. 
    - Maxwell, John (1 November 2013). "Building Publishing Workflows with Pandoc and Git". Publishing @ SFU. https://publishing.sfu.ca/2013/11/building-publishing-workflows-with-pandoc-and-git/. 
    - Krewinkel, Albert; Robert Winkler (8 May 2017). "Formatting Open Science: agilely creating multiple document formats for academic manuscripts with Pandoc Scholar". PeerJ Computer Science 3: e112. doi:10.7717/peerj-cs.112. https://peerj.com/articles/cs-112/. Retrieved 25 May 2017. 
  3. "John MacFarlane". University of California, Berkeley. https://philosophy.berkeley.edu/people/detail/1. 
  4. "Pandoc User's Guide". Description. https://pandoc.org/MANUAL.html#description. "...one should not expect perfect conversions between every format and every other. Pandoc attempts to preserve the structural elements of a document, but not formatting details..." 
  5. Fenner, Martin (12 December 2013). "From Markdown to JATS XML in one Step". Gobbledygook. doi:10.53731/r294649-6f79289-8cw0k. http://blog.martinfenner.org/2013/12/12/from-markdown-to-jats-xml-in-one-step/. Retrieved 27 June 2014. 
  6. 6.0 6.1 "Citations". Pandoc User's Guide. https://pandoc.org/MANUAL.html#citations. 
  7. Tenen, Dennis; Grant Wythoff (19 March 2014). "Sustainable Authorship in Plain Text using Pandoc and Markdown". The Programming Historian (3). doi:10.46430/phen0041. http://programminghistorian.org/lessons/sustainable-authorship-in-plain-text-using-pandoc-and-markdown. Retrieved 27 June 2014. 
  8. Denlinger, Kyle. "Research Guides: Zotero: Citations & Bibliographies" (in en). https://guides.zsr.wfu.edu/zotero/citations. 
  9. "Pandoc's Markdown". Pandoc User's Guide. https://pandoc.org/MANUAL.html#pandocs-markdown. 
  10. Mullen, Lincoln (20 March 2012). "Make Your Own E-Books with Pandoc". The Chronicle of Higher Education Blogs: ProfHacker. http://chronicle.com/blogs/profhacker/make-your-own-e-books-with-pandoc/39067. 
  11. "Getting started with pandoc". Creating a PDF. https://pandoc.org/getting-started.html#creating-a-pdf. 
  12. See as an example MacFarlane, John (17 May 2014). "Pandoc for Haskell Hackers". BayHac 2014, Mountain View, CA. http://johnmacfarlane.net/BayHac2014/.  The source file is written in Markdown.

External links