This page aggregates blog entries by people who are writing about TeX and related topics.
Today’s post is a short introduction to digital scholarly editing. I will explain some basic principles (so mostly theory) and point you to a few resources you will need to get started in a more practical fashion. I’m teaching a class on digital scholarly editing this term, so I thought I could use the opportunity to write an intro post on this important topic. How does a Digital Edition relate to an analogue scholarly edition? Unlike analogue scholarly editons, digital editions are not exclusive to text and they overcome the limitations of print by following what we call a digital paradigm rather than an analogue one. This means that a digital edition cannot be given in print without loss of content or functionality. A retrodigitized edition (an existing analogue edition which is digitized and made available online), thus, isn’t enough to qualify as a digital edition because it follows the analogue paradigm. Ergo: It’s not about the storage medium. Aread more What you really need to know about Digital Scholarly Editing
It is quite natural to think that separating a word up into individual characters is quite easy. It turns out that for the computer this isn’t really the case. If we look at a system that understands Unicode (like XeTeX or LuaTeX), most of the time one ‘character’ is stored as one codepoint. A codepoint is a single character entity for a Unicode programme. For example, if we take the input café, it is made up of four codepoints: U+0063 (LATIN SMALL LETTER C) U+0061 (LATIN SMALL LETTER A) U+0066 (LATIN SMALL LETTER F) U+00E9 (LATIN SMALL LETTER E WITH ACUTE) So we could in XeTeX/LuaTeX use a simple mapping to grab one character at a time and do stuff with it. However, that’s not always the case. Take for example Spın̈al Tap. The dotless-i is a single codepoint, but there is not a codepoint for an umlauted-n. Instead, that is represented by two codepoints: a normal n and a combining umlaut. As a user, it’s clear that we’d want to get a single ‘character’ here. So there’s clearly more work to do. Luckily, this is not just a TeX problem and the Unicode Consortium have thought about it for ...
Today’s post is a quick introduction to version control as a concept and version control systems. It explains what they are and why you should be using them. I was just sending one of my best old-timey blogposts to a friend (How to quit MS Word for good), ended up re-reading it and realized that therein, I had promised that I would write a blog post on version control some day. And, if I’m not mistaken, I never followed up on that. So here you are, a short post on version control just to keep things going on the blog. What is Version Control? So I read this book a few years ago. The Complete Software Developer’s Career Guide: How to Learn Programming Languages Quickly, Ace Your Programming Interview, and Land Your Software Developer Dream Job by John Sonmez (Simple Programmer 2017). While I’m not that fond of its author anymore since I realized that he uses his platform toread more A Primer on Version Control and Why You Need It
A topic that comes up for many LaTeX users is how best to mark up math mode in sentences: inline math mode. LaTeX offers three (!) official ways to do that $...$ \(...\) \begin{math} ... \end{math} The last version is clearly far too verbose for routine use, but the first and second approaches have a much less clear-cut division. Plain TeX uses the $...$ construct exclusively, and that means many experienced (La)TeX users simply use this without any further consideration. There are good arguments in favour of the syntax, most obviously that this switches directly into math mode (it uses the underlying TeX idea of category codes with no macro expansion required). On the other hand, it lacks any possiblity of mathcing begin and end points. LaTeX’s \(...\) syntax was introduced by Lamport early in the development of the format. Using separate begin and end marks means that is does allow error detection in the editor, and it also is linked visually to LaTeX’s display math \[...\] approach. (More on that below.) So which one to use? Experience suggests that whilst Lamport made many good decisions in the design of LaTeX’s input syntax, \(.,..\) wasn’t the best of them. The ...
TUGboat volume 43, number 2, has been mailed to TUG members. It is also available online and from the TUG store. In addition, prior TUGboat issue 43:1 is now publicly available. Submissions for the next issue are welcome; the deadline is October 15, 2022 (early submissions are especially appreciated). Finally, please consider joining or renewing your TUG membership if you haven't already (we'll send this issue immediately), and thanks.
Today’s post is my long-awaited take on typesetting scholarly editons using the reledmac package. Not only does it introduce theread more Enough reledmac to be dangerous: Scholarly Editing with LaTeX & XSLT
This post is another reflection on the relationship between teaching and self-directed learning. It focuses on how to find a balance with making learning too hard or not hard enough. Thus the title: How can we deliberately make ourselves and/or our students fail just hard enough to learn? Context: I just found this post in the huge number of unfinished drafts in my WordPress. It was almost done, supposedly from early fall 2021. Some of it are reflections on my own (online) teaching in the summer term of 2021. I thought this was an interesting reflection still, so I decided to fix it up a little and post it now, despite the text not being “new” and some of my thoughts on my own teaching having changed over the last year where I have been teaching more than before as a Postdoc. Because the draft of this post was already so long and got a little longer with some 2022read more Failing just hard enough to learn [Learning & Teaching / Riding higher waves Pt. 2.1]
Bei golem.de wurde mein zweiter LaTeX-Artikel veröffentlicht, ihr findet ihn hier: https://www.golem.de/news/layouten-mit-latex-setzt-du-noch-oder-gestaltest-du-schon-2207-165543.html Der erste Artikel zum Thema befindet sich hier: https://www.golem.de/news/latex-schreibst-du-noch-oder-setzt-du-schon-2201-162303.html UweUwe Ziegenhagen likes LaTeX and Python, sometimes even combined. Do you like my content and would like to thank me for it? Consider making a small donation to my local fablab, the Dingfabrik Köln. […]
Hier die Folien meines MyTinyTodo2LaTeX Lightning Talks, gehalten auf der Sommertagung 2022 von Dante e.V. in Magdeburg. Folien UweUwe Ziegenhagen likes LaTeX and Python, sometimes even combined. Do you like my content and would like to thank me for it? Consider making a small donation to my local fablab, the Dingfabrik Köln. Details on how […]
Hier die Folien meines „Beamer Themes“-Vortrags bei der Dante Sommertagung in Magdeburg. FolienFolien UweUwe Ziegenhagen likes LaTeX and Python, sometimes even combined. Do you like my content and would like to thank me for it? Consider making a small donation to my local fablab, the Dingfabrik Köln. Details on how to donate can be found […]
Unter https://github.com/UweZiegenhagen/LaTeX-Beamer-Theme-Overview habe ich ein Projekt begonnen, das alle in einem TeX Live vorhandenen Beamer-Themes anhand von Beispielbildern vorstellt. Direkter Link zur Übersicht: https://github.com/UweZiegenhagen/LaTeX-Beamer-Theme-Overview/blob/main/OVERVIEW.md Technisch funktioniert es so, dass der Name des Themes aus dem Dateinamen extrahiert wird, dazu nutze ich mein Varsfromjobname-Paket. Die einzelnen PDFs werden dann über ein Python-Skript mit LaTeX erzeugt, mittels […]
Für LuaLaTeX gibt es mit showhyphenation und showkerning zwei interessante Pakete, die die möglichen Trennstellen bzw. das Kerning anzeigen. %!TEX TS-program = lualatex \documentclass[12pt,ngerman]{scrartcl} \usepackage[utf8]{inputenc} \usepackage[T1]{fontenc} \usepackage{babel} \usepackage{blindtext} \usepackage{microtype} \usepackage{showhyphenation} \usepackage[ontop]{showkerning} \begin{document} \blindtext \blindtext \end{document} UweUwe Ziegenhagen likes LaTeX and Python, sometimes even combined. Do you like my content and would like to thank me […]
The deadline to receive presentation proposals for the TUG'22 conference is June 15, about a week from now. The conference will be held online July 22-24. It would be great to receive more proposals, so if there's anything TeX- or typography-related you'd like to give a talk on, don't hesitate to send in a title and abstract. Presentations are usually around 30min, but shorter or longer is fine. We also greatly appreciate accompanying papers for the TUGboat proceedings (deadline: July 31), but this is not a requirement. Registration for the conference is free. Thanks for considering, and hope to see you there. --happy TeXing, karl. P.S. Please feel free to redistribute this note elsewhere. The more widely it goes out, the better.
Following up from the previous post Using APA7 with umalayathesis, but about usmsthesis. Likewise, I am hoping (against hope?) that one day, apacite package will be updated to support APA7, so that usmthesis.cls won’t need to undergo overhauling either. But until that day comes, if you need to use APA7 with usmthesis now, then it […]
Currently the umalayathesis class uses apacite to implement the bibliography style, but apacite supports only APA6. For full APA7 it would be necessary to use biblatex-apa; no BibTeX style for full APA7 exists yet. I’m still hoping (against hope?) that one day, the apacite package will be updated to support APA7, so that umalayathesis.cls won’t […]
Subscribe to the TeX community RSS feed
Do you write about TeX and related topics? Let us know and we will add your feed to this page.