tl;dr If you want to skip the explanation and justification for why you might want separate bibliographies, you can skip down to the example section, or just go see some example files at GitHub. Why use separate bibliographies? In academic articles, it’s common to have a supplemental appendix with extra tables, figures, robustness checks, additional math, proofs, and other details.

Merci à Hugo Gruson pour ses commentaires utiles sur cette traduction! Le logiciel libre Pandoc par John MacFarlane est un outil très utile : par exemple, Yanina Bellini Saibene, community manager de rOpenSci, a récemment demandé à Maëlle si elle pouvait convertir un document Google en livre Quarto.Maëlle a répondu à la demande en combinant Pandoc (conversion de docx en HTML puis en Markdown par le biais de pandoc::pandoc_convert()) et

The Pandoc CLI by John MacFarlane is a really useful tool: for instance, rOpenSci community manager Yanina Bellini Saibene recently asked Maëlle whether she could convert a Google Document into a Quarto book.Maëlle solved the request with a combination of Pandoc (conversion from docx to HTML then to Markdown through pandoc::pandoc_convert()) and XPath.You can find the resulting experimental package quartificate on GitHub.Pandoc is not only

Pandoc-flavored Markdown makes it really easy to cite and reference things. You can write something like this (assuming you use this references.bib BibTeX file): --- title: "Some title" bibliography: references.bib --- According to @Lovelace:1842, computers can calculate things.

My longstanding workflow for writing, citing, and PDF management When I started my first master’s degree program in 2008, I decided to stop using Word for all my academic writing and instead use plain text Markdown for everything. Markdown itself had been a thing for 4 years, and MultiMarkdown—a pandoc-like extension of Markdown that could handle BibTeX bibliographies—was brand new.

Pandoc’s Markdown allows for “fancy lists”, i.e., lists with different styles used for the marker of ordered list items. E.g., the list (I) primus (#) secundus (#) tertius uses uppercase roman numerals and double parentheses for the markers. It gets rendered as Continuations The fancy lists feature also allows to continue lists after an intermediate paragraph: i. one #. another Interruption; not part of any list. iii.

Pandoc’s Markdown allows for “fancy lists”, i.e., lists with different styles used for the marker of ordered list items. E.g., the list (I) primus (#) secundus (#) tertius uses uppercase roman numerals and double parentheses for the markers. It gets rendered as primus secundus tertius Continuations The fancy lists feature also allows to continue lists after an intermediate paragraph: i. one #. another Interruption;

Line breaks usually have no semantic meaning within a Markdown paragraph. However, using line breaks to mark the end of a sentece can help with productivity for various reasons. ¹ Documents with one sentence per line are also called “ventilated prose”, and the Write the {Ascii}Docs website has a good article on that topic.

Line breaks usually have no semantic meaning within a Markdown paragraph. However, using line breaks to mark the end of a sentece can help with productivity for various reasons.¹ Documents with one sentence per line are also called “ventilated prose”, and the Write the {Ascii}Docs website has a good article on that topic.

When extending pandoc (or Quarto) with Lua filters, we interact with so-called Lua userdata objects. These objects are used to wrap document AST elements, making them accessible from Lua scripts. They mostly behave like normal Lua tables. This post is intended as a quick overview, listing interesting properties of userdata objects.