Pandoc

Pandoc
Original author(s) John MacFarlane
Initial release 10 August 2006 (2006-08-10)
Stable release
1.17.0.3 / 24 March 2016 (2016-03-24)
Repository github.com/jgm/pandoc
Development status Active
Written in Haskell
Operating system Unix-like, OS X, Windows
Licence GNU General Public License
Website pandoc.org

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

Supported file formats

Pandoc's most thoroughly supported file format is an extended version of Markdown, but it can also read many other forms of lightweight markup language, HTML, ReStructuredText, LaTeX, OPML, Org-mode, DocBook, and Office Open XML (Microsoft Word .docx).

It can be used to create files in many more formats, including Office Open XML, OpenDocument, HTML, Wiki markup, InDesign ICML, web-based slideshows,[9] ebooks,[10] OPML, and various TeX formats (through which it can produce a PDF). It has built-in support for converting LaTeX mathematical equations to MathML and MathJax, among other formats.

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.[11]

Integration with reference managers

An included module, pandoc-citeproc, allows the program to use data from reference management software such as BibTeX, EndNote, Mendeley, or Papers. It has the ability to integrate directly with Zotero.[12] 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. This allows the program to serve as a simpler alternative to LaTeX for producing academic writing.[13]

References

  1. Mullen, Lincoln (2012-02-23). "Pandoc Converts All Your (Text) Documents". The Chronicle of Higher Education Blogs: ProfHacker. Retrieved 2014-06-27.
  2. McDaniel, W. Caleb (2012-09-28). "Why (and How) I Wrote My Academic Book in Plain Text". W. Caleb McDaniel at Rice University. Retrieved 2014-06-27.
  3. Healy, Kieran (2014-01-23). "Plain Text, Papers, Pandoc". Retrieved 2014-06-27.
  4. 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.
  5. Till, Kaitlyn; Shed Simas; Velma Larkai (2014-04-14). "The Flying Narwhal: Small mag workflow". Publishing @ SFU. Retrieved 2014-06-27.
  6. Maxwell, John (2013-11-01). "Building Publishing Workflows with Pandoc and Git". Publishing @ SFU. Retrieved 2014-06-27.
  7. Maxwell, John (2014-02-26). "On Pandoc". eBound Canada: Digital Production Workshop, Vancouver, BC. Retrieved 2014-06-27.
  8. "John MacFarlane". Department of Philosophy. University of California, Berkeley. Retrieved 25 July 2014.
  9. See as an example MacFarlane, John (2014-05-17). "Pandoc for Haskell Hackers". BayHac 2014, Mountain View, CA. Retrieved 2014-06-27. The source file is written in Markdown.
  10. Mullen, Lincoln (2012-03-20). "Make Your Own E-Books with Pandoc". The Chronicle of Higher Education Blogs: ProfHacker. Retrieved 2014-06-27.
  11. Fenner, Martin (2013-12-12). "From Markdown to JATS XML in one Step". Gobbledygook. Retrieved 2014-06-27.
  12. Hetzner, Erik (2014-06-25). "zotxt". Retrieved 2014-06-27.
  13. Tenen, Dennis; Grant Wythoff (2014-03-19). "Sustainable Authorship in Plain Text using Pandoc and Markdown". The Programming Historian. Retrieved 2014-06-27.

External links

This article is issued from Wikipedia - version of the 11/13/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.