Setting the document font this way works for ConTeXt, LaTeX, and HTML output. The fonts used in docx or odt output must be controlled with the reference document instead. The default LaTeX engine is pdflatex, which only supports TeX’s own font format and cannot use the TrueType or OpenType fonts installed on the system. However, XeLaTeX was written with that in mind; switching to that engine allows to specify any font available on the system.
When pandoc is used in larger pipelines, e.g. in combination with Sphinx, it can be useful to pack everything up into one neat container. One option is to base the container on a pandoc image like pandoc/core, but this may be difficult due to other dependencies.
Setting the document font this way works for ConTeXt, LaTeX, and HTML output. The fonts used in docx or odt output must be controlled with the reference document instead. The default LaTeX engine is pdflatex, which only supports TeX’s own font format and cannot use the TrueType or OpenType fonts installed on the system. However, XeLaTeX was written with that in mind; switching to that engine allows to specify any font available on the system.
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.
I recently made my first R package and was asked how I did it. The answer of course was: I searched, read, and stumbled around until it was done. But having gone through the process I figured it was worthwhile summarising what I did and what I found tricky. First off, there are a ton of resources out there that describe how to go about building a package.
In this post, the authors celebrate the 10th anniversary of re3data, sharing insights about the history, the service itself, and how it has developed over the last decade. The post was published simultaneously on the DataCite Blog. The re3data registry went online in 2012 and is celebrating a decade of curation and making information about data repositories available to the research community.
A short post to announce TrackMateR, a new R package to analyse TrackMate XML outputs. Code Instructions Background TrackMate is a plug-in for ImageJ which ships with Fiji. It’s essential for single particle tracking work, particularly for microscopy movies. For example, tracking the movement of fluorescent vesicles inside cells. A tracking session generates a TrackMate XML file.
Taxonomic treatments have come up in various discussions I'm involved in, and I'm curious as to whether they are actually being used, in particular, whether they are actually being cited. Consider the following quote: "Traditional" academic citation is from article to article.
Feature images are commonly used for blog posts, including on this blog. We can use our screenshots or photos or stock photos (ideally license free or with an open license) from sites like Flickr, Unsplash, or Pexels. More recently, we can also use artificial intelligence tools such as DALL·E 2 that generate images from a description in natural language.
Dear rOpenSci friends, it’s time for our monthly news roundup! You can read this post on our blog.Now let’s dive into the activity at and around rOpenSci!rOpenSci HQ Coworking sessions resume! Join us for social coworking & office hours monthly on first Tuesdays!Hosted by Steffi LaZerte and various community hosts.Everyone welcome.No RSVP needed.Consult our Events page to find your local time and how to join.