Final pre-release of LaTeX 2023-06-01 is available for testing

We submitted the final pre-release version for the 2023-06-01 LaTeX kernel to CTAN recently. It should have made its way into TeX Live for everyone by now (or pretty soon), so it’s ready for users and developers to try.

We did not manage to get everything in that we originally planned for the June release, but given that the newsletter has seven pages is some indication that we have been busy. Please test it out so that we all can be sure that the main release has no issues. Given that we are somewhat late in the schedule we will delay the June release by a week or two so that developers can verify that their packages will work smoothly with the new release.

Automated tagging of PDF documents

We have now enabled new automatic tagging functionality for additional LaTeX elements, among them most display environments, standard sectioning commands and content, figure and table listings. Also supported are standard floats, citations, bibliographies and a few more elements, but we aren’t yet at the point that we can state that all elements described in Leslie Lamport’s manual on LaTeX are supported — but we are getting close.

This can be activated through

\DocumentMetadata{testphase=phase-III}
\documentclass{...}                     % article, book or report

In addition there is also an early prototype for tagging formulas, which can be activated through

\DocumentMetadata{testphase={phase-III,math}}
\documentclass{...}

It offers support for LaTeX’s standard math environments and also for all environments provided through the amsmath package.

All of this automation is currently in a prototype state and restricted to the use of standard classes (article, report, and book) and it supports only a limited number of add-on package. See the LaTeX2e News Issue 37 newsletter for further details. It provides information how to submit feedback on the new functionality.

The newsletter also covers various other small enhancements or corrections that we provide with the June release.

Testing

Processing your documents with the pre-release is straightforward. All you have to do is to replace the invocation command by appending -dev to the executable, e.g., on the command line you would run

• pdflatex-dev myfile or
• lualatex-dev myfile or
• xelatex-dev myfile

instead of using pdflatex, lualatex or xelatex. If you use an integrated editing environment, then it depends on the system how to configure it to use an alternative format; but in any case the necessary modification should be straightforward.

Enjoy — Frank

The third edition of The LaTeX Companion is available for pre-order

I’m happy to announce that the third edition of The LaTeX Companion has been sent to the printer and is now available for pre-order. It will be published by end of April or beginning of May. This is the end of five years of careful work and we hope that it will provide our readers with all the information they need to successfully navigate the LaTeX ecosystem and efficiently produce beautiful documents.

Since the publication of the last edition (2004) a lot has happened in the LaTeX world and thus a complete rewrite was necessary.
All chapters have been thoroughly revised and in many cases largely extended to describe new important functionality and features. More than 5,000 add-on packages have been analyzed in detail, out of which roughly 10% have been chosen for inclusion in The LaTeX Companion. All important aspects of these packages are described to provide the user once again with a satisfying one-stop–shop experience for the decade to come.

To cover what we thought worth describing today, the book nearly doubled in size. The print edition is therefore produced as a two-volume set and sold as a bundle. Both volumes come as hardcover with ribbons to easily mark pages in the book.

To give you an idea of what is covered in the third edition, here are some excerpts:

• Preface of the 3rd edition (317 kB)
• Table of contents (337 kB)
• The initial pages of all twenty chapters (3,4 MB)

The edition is also available as an eBook (Part I and II combined) consisting of PDF and ePub format without DRM. Finally, the publisher offers the combination of the printed books + the digital versions at a very attractive price not available anywhere else.
Note that some distributors offer the two parts of the edition (also) individually, but usually for a much higher price compared to the bundle. Also important is that the digital version offered by some resellers only contains either the ePub or the PDF but not both! We therefore recommend that you watch out for this.

In Europe it might be easier to buy the print edition from bookshops or from resellers such as Amazon to avoid having to deal with import/customs fees, e.g. by using Amazon.de in Germany. However, the combination of print and digital formats is only available from the publisher’s InformIT site through the link above.

Happy LaTeXing — Frank

Towards automated PDF tagging: Pre-release of LaTeX 2023-06-01 is available for testing

We submitted the second pre-release version for the 2023-06-01 LaTeX kernel to CTAN recently. It should have made its way into TeX Live (both 2022 and the 2023 pre-test) for everyone by now, so it’s ready for users to try.

It does not yet contain all updates to the LaTeX format that will become part of the standard in June, but the new code already provided is worth checking out.

Automated tagging of PDF documents

We have now enabled new automatic tagging functionality for additional LaTeX elements, among them most display environments, standard sectioning commands and content, figure and table listings.

This can be activated through

\DocumentMetadata{testphase=phase-III}
\documentclass{...}                     % article, book or report

In addition there is also a (very early) prototype for tagging formulas, which can be activated through

\DocumentMetadata{testphase={phase-III,math}}
\documentclass{...}

It offers support for LaTeX’s standard math environments but also for all environments provided through the amsmath package.

All of this automation is currently in a prototype state and restricted to the use of standard classes (article, report, and book) and it supports only a limited number of add-on package. See the draft version of the LaTeX2e News Issue 37 newsletter for further details. It provides information how to submit feedback on the new functionality.

The newsletter also covers various other small enhancements or corrections that we intend to provide with the June release.

Outlook

We expect to produce another pre-release around the end of April, which will give us time to finish the release by June. Please help with the testing.

Processing your documents with the pre-release is straightforward. All you have to do is to replace the invocation command by appending -dev to the executable, e.g., on the command line you would run

• pdflatex-dev myfile or
• lualatex-dev myfile or
• xelatex-dev myfile

instead of using pdflatex, lualatex or xelatex. If you use an integrated editing environment, then it depends on the system how to configure it to use an alternative format; but in any case the necessary modification should be straightforward.

Enjoy — Frank

PDF days Europe 2022 - Tagged and Accessible LaTeX

Photo by Catrin Wolf

At the PDF days Europe 2022 conference, hosted by the PDF Association (PDFA) we gave a presentation on the current state of the “LaTeX Tagged PDF” project, explaining the challenges, achievements, and our plans for the future.

The talk was recorded and is now available on the PDFA website through this link.
The slides of the presentation are available here.

The November 2022 release of LaTeX is available

More or less on time we released the 2022-11-01 version of LaTeX and by now it should be available in all major distributions. This release is largely a consolidation release. However it also contains one very important enhancement that is initially important for package developers, but over time — when the kernel and packages starting using it — will become relevant for user documents.

I’m talking about the fact that we prepared the grounds to use optional key/value arguments with basically any command including those that current have optional arguments expecting a simple value. For example, \chapter or \caption allow an optional argument to hold the data for the TOC or LOF file. With the new functionality they can be changed (not done yet) to alternatively support a key/value list in this argument and LaTeX will automatically determine which version applies. This is very important for providing a standard and consistent method for accessible LaTeX documents, because there has to be a possibility to specify “alternative text” in various places. There are other reasons related to the Tagged PDF project why such an interface is useful and the beauty of it is that it is both consistent and upward compatible.

To get a good overview about the new features and most of the important bug fixes made in this release take a look at “LaTeX2e News Issue 36”. This document should be accessible through texdoc ltnews36 on your computer and can also be found on the LaTeX2e news page where you will also find release information for earlier LaTeX releases.

Happy LaTeXing — Frank

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:

1. U+0063 (LATIN SMALL LETTER C)
2. U+0061 (LATIN SMALL LETTER A)
3. U+0066 (LATIN SMALL LETTER F)
4. 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 us. They provide a data file and rules that describe how to divide input into graphemes: ‘user perceived characters’. So ‘all’ that is needed is to examine the input using these rules, and to divide it up so that ‘characters’ stay together.

For pdfTeX, there’s an additional wrinkle: it uses bytes, not codepoints, and so if we use a naïve TeX mapping, we would divide up any codepoint outside the ASCII range into separate bytes: not good. Luckily, the nature of codepoints is predictable: all that is needed is to examine the first byte and collect the right number of further bytes to re-combine into a valid codepoint.

This work isn’t something the average end user wants to do. Luckily, they don’t have to as the LaTeX team have looked at this and created a suitable set of expl3 functions to do it: \text_map_function:nN and \text_map_inline:nn. So for example we can do

\ExplSyntaxOn
\text_map_inline:nn { Spın̈al ~ Tap } { (#1) }
\ExplSyntaxOff

and get

(S)(p)(ı)(n̈)(a)(l)( )(T)(a)(p)

in any TeX engine (assuming we are set up to print the characters, of course).

Taking a more ‘serious’ example (And one that is going to use LuaTeX for font reasons), we might want to map over Bangla text. It’s easy to do that with the expl3 function \tl_map_inline:nn, but it gives very odd results. In contrast, \text_map_inline:nn divides up the characters correctly.

\documentclass{article}
\usepackage{fontspec}
\newfontface\harfbengali
  {NotoSansBengali-VariableFont_wdth,wght.ttf}[Renderer=HarfBuzz,Script=Bengali]
\begin{document}
\harfbengali
\ExplSyntaxOn
ন্দ্রকিন্দ্র
\par
\text_map_inline:nn{ন্দ্রকিন্দ্র}{(#1)}
\par
\tl_map_inline:nn{ন্দ্রকিন্দ্র}{(#1)}
\ExplSyntaxOff
\end{document}

which gives (You’ll need Noto Sans Bengali available to make this work locally.)

So, as you can see, mapping to ‘real’ text is easy with expl3: you just need to know that the tools are there.

Pre-release of LaTeX for 2022-11-01 is ready for testing

We submitted the first pre-release version for the 2022-11-01 LaTeX kernel to CTAN recently. It should have made its way into TeX Live or should appear for everyone pretty soon.

It already contains most updates and improvements to the LaTeX format that will become part of the standard in November; thus testing them now will help identifying packages that need upgrading and finding any bugs lurking before that release hits the streets; see below for how to do this in a safe way.

The main highlight is briefly discussed below, further details plus smaller bug fixes and improvements not covered here can be found in the draft version of the LaTeX2e News Issue 36 newsletter.

New feature in the kernel (highlights)

For developers

The most important improvement in the LaTeX kernel is to offer a standard mechanism for receiving and manipulating key/value arguments in commands. This is implemented in the \DeclareDocumentCommand interfaces and offers a reliable method to allow an (optional) argument to contain either a key/value list or to interpret it as an ordinary argument if the content does not contain such a key/value list. In the latter case that content is interpreted as the value of the key whose name is specified in the command declaration. For example, the \caption command could be declared as

\DeclareDocumentCommand \caption {s ={short-text}+O{#3} +m}
       {...}

which means that it expects an optional star (s) and a mandatory argument that can contain \par commands (+m). It also has an optional argument (before the mandatory one) whose default – if not given – is the content of the mandatory one (+O{#3}), which is why it refers to #3. By prefixing this with ={short-text} we state that this optional argument should check for a key/value list and if no such list is found, should assign its argument content to the key short-text for further processing. Then such processing of the argument can always assume that it got a key/value list, either the one specified or the simple one with just the short-text key.

Right now, only the functionality is offered and that is largely targeted towards developers. However, the moment commands make use of that feature (and from the project team perspective we certainly intend to make use of it in upcoming releases) it becomes relevant for users as well, because then they will be able to specify key/value arguments in several places, while support for “free text arguments” is retained.

While technically this functionality can be used with any argument we intend to use it only for the first optional argument of a command and suggest that developers do likewise so that (most) LaTeX commands use a similar interface that makes it easy for users to work with, i.e.,

\cmd * [<arg with key/val or free text>] <other mandatory or optional arguments>

Simpler commands could, of course, offer

• no * form or
• an optional argument always expecting a key/value list or
• one without any key/value support or
• no optional argument whatsoever.

For developers and users

You may wonder what rules are used to determine that an argument is interpreted as a key/value list. They are fairly simple, but adequate (we hope) for nearly all use cases. Basically, the argument text is searched for one or more = signs that are neither within an explicit brace group {...} nor part of inline math mode, or more precisely not within $...$ or \(...\). Other constructs are not considered at the moment, e.g., if you really use \begin{math}...\end{math} or some display math that contains an equal sign, it will not work inside such an argument without adjustment. If the content is incorrectly interpreted as a key/value list, then the remedy for the user is to hide the content in a brace group, e.g.,

\caption[The form: \begin{math} a=b\end{math}]  {...}  % fails
\caption[{The form: \begin{math} a=b\end{math}}]{...}  % works

There is also a way to force interpretation as a key/value list by prepending =, to the argument which can be useful in some situations with valueless keys. More details can be found in the documentation.

Outlook

We expect to produce another pre-release before the next main release, but this will most likely only contain some further updates to the latex-lab code, and possible some minor updates to fix one or the other minor pending issue. Please help with the testing of this pre-release by using it for your documents or testing it against your own packages.

Processing your documents with the pre-release is straightforward. All you have to do is to replace the invocation command by appending -dev to the executable, e.g., on the command line you would run

• pdflatex-dev myfile or
• lualatex-dev myfile or
• xelatex-dev myfile

instead of using pdflatex, lualatex or xelatex. If you use an integrated editing environment, then it depends on the system how to configure it to use an alternative format; but in any case the necessary modification should be straightforward.

Enjoy — Frank & Joseph

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 matching 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 number of times that pair-matching is helpful simply doesn’t compete with the extra complexity of the input. At the same time, there’s no difference in the results between the two syntax, so there isn’t a downside to using $..$. So I (and the majority of the current LaTeX team) favour using $..$.

I think it’s important to contrast with (unnumbered) display math mode. There, the LaTeX \[...\] syntax is the officially-supported approach, and the plain TeX $$..$$ is not. For display math, there are significant differences in what can be done using \[...\] compared to directly switching to TeX’s display math mode using $$..$$, and so the situation is clear: use \[...\].

Talks from the online TUG Conference 2021 and 2022 on YouTube

For some reason it took a long time to get the 2021 talks cut and uploaded to YouTube and when that finally happened, I was in the middle of entering copy-editing corrections for the LaTeX Companion, 3rd edition and simply missed the opportunity to announce the talks and update the website to refer to it. Now with with TUG 2022 also online this is more than overdue.

Both conferences (as usual) had quite a number of interesting talks on many subjects of TeX usage and related topics. If you have missed the conferences (or if you want listen to one of the talks again) you will find them all on the TeX Users Group Channel on YouTube.

There were also several talks by members of the LaTeX Project team. Some are directly relevant to our multi-year project on automatically producing tagged PDF; others discuss other LaTeX topics of interest. As an intro to the tagged-PDF project (for those who haven’t heard about it yet) I also provide one link to a talk from the 2020 conference announcing that project.

• 2020 Conference
  • Frank Mittelbach: Quo Vadis LaTeX(3) — A look at the upcoming years (2020) which gives an overview about our recently started multi-year project that aims at providing accessible and tagged PDF. There is also an article related to the information given in the talk.
• 2021 Conference

  • Frank Mittelbach: Taming the beast — Advances in paragraph tagging with pdfTeX and XeTeX (2021) - Automatic paragraph tagging with the pdfTeX and XeTeX engine now possible.

  • Ulrike Fischer: On the road to Tagged PDF: About StructElem, Marked Content, PDF/A and Squeezed Bärs (2021) — An overview about tagging possibilities already available. There is also an article related to the talk.

  • Marcel Krüger: Reviving Type 3 fonts for modern LuaLaTeX documents — A discussion of the recently added LuaTeX support for this font format for non-bitmap use cases.

  • Joseph Wright: Any colo(u)r you like (2021) — New color-handling methods for the LaTeX kernel.

  • Paulo Ney de Souza: Interview with Frank Mittelbach (2021) — This interview took place on 7 August 2021, during the TUG 2021 online conference. It is also transcribed as an article.

• 2022 Conference

  • Ulrike Fischer: New in stock — recent LaTeX improvements (that you may have missed), (2022) — An overview about selected new features offered by LaTeX with a number of examples given.

  • Ulrike Fischer: Using spot colors with LaTeX (2022) — Experience gained while working on the 3rd edition of The LaTeX Companion

  • Joseph Wright: Key-value setting handling in the kernel (2022) — A discussion of new features for packages and classes offering key/value options.

  • Joseph Wright: Case changing: LaTeX reaches Unicode-land (2022) — LaTeX now provides much better support for case changing.

  • Joseph Wright: siunitx: Launching version 3 (2022) — A discussion of the move from siunitx version 2 to version 3 and what developer efforts have made this a success.

Enjoy — Frank

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

Uwe

Uwe 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 here Spenden für die Dingfabrik.

More Posts - Website

Hier die Folien meines MyTinyTodo2LaTeX Lightning Talks, gehalten auf der Sommertagung 2022 von Dante e.V. in Magdeburg.

Folien

Uwe

Uwe 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 here Spenden für die Dingfabrik.

More Posts - Website

Hier die Folien meines „Beamer Themes“-Vortrags bei der Dante Sommertagung in Magdeburg.

FolienFolien

Uwe

Uwe 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 here Spenden für die Dingfabrik.

More Posts - Website

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 imagemagick in einzelne PNGs zerlegt und in der Overview.md verlinkt.

Hinweis: Nicht bei allen in TeX Live vorhandenen Themes funktioniert dieser Weg, die Autoren der nicht funktionierenden Themes werde ich anschreiben.

Uwe

Uwe 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 here Spenden für die Dingfabrik.

More Posts - Website

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}

Uwe

Uwe 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 here Spenden für die Dingfabrik.

More Posts - Website

The June 2022 LaTeX release is available

With a few days delay we released the 2022-06-01 version of LaTeX and by now it should be available in all major distributions. The release contains a number of important improvements and extensions that have be discussed in previous posts.

To get a good overview about the new features and most of the important bug fixes made in this release take a look at “LaTeX2e News Issue 35”. This document should be accessible through texdoc ltnews35 on your computer and can also be found on the LaTeX2e news page where you will also find release information for earlier LaTeX releases.

With the extended testing of pre-releases I would have hoped for once that we can do without having to produce a patch release soon after, but no such luck. While no code issues have been found, we managed to mess up the banner, which comes out as

LaTeX2e <2022-06-01> pre-release-0 (develop 2022-6-12 branch)
L3 programming layer <2022-06-02>

which is, of course, utter nonsense. So expect a patch release during the next days (it will be identical to the current one, except for a corrected banner, a minor fix in for legacy Cyrillic code pages, and a fix for ltxdoc if used with csquotesin the preamble).

Happy LaTeXing — Frank

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.

Final pre-release of LaTeX for 2022-06-01ready for testing

Last week we submitted the final pre-release version for the 2022-06-01 LaTeX kernel so it should be available in all major TeX distributions.

As always new functionality and bug fixes are discussed in the corresponding LaTeX2e News Issue 35 newsletter.

Because we are a few days behind our original schedule, we are going to delay the main release for a few days too, to give people time to do some final testing. Please help with this testing!

Processing your documents with the pre-release is straightforward. All you have to do is to replace the invocation command by appending -dev to the executable, e.g., on the command line you would run

• pdflatex-dev myfile or
• lualatex-dev myfile or
• xelatex-dev myfile

instead of using pdflatex, lualatex or xelatex. If you use an integrated editing environment, then it depends on the system how to configure it to use an alternative format; but in any case the necessary modification should be straightforward.

Enjoy — Frank

I mentioned recently that I’m working on features for siunitx v3.1. One area that I’ve now been able to commit is improvements to handling complex values.

In v2, you could give complex values in the normal argument to \num or \SI. I removed that for v3, and of course that was not entirely popular. Instead, I introduced dedicated commands, \complexnum and \complexqty. Part of the reason for that was that it makes the implementation of \num and \qty/\SI easier. But the other was that I wanted to address polar form, and that really didn’t look viable if it was mixed in with the normal numerical argument type.

I’ve now committed a change that introduces support for polar form in siunitx. So what happens now is if you give a value such as \num{10:30}, it’s treated as a magnitude and an angle. The latter has a setting to determine if it’s regarded as being in degrees or radians. The package can then typeset the result in a similar form, using the \angle symbol between the two parts. You can also set up to convert between the classical (Cartesian) and polar forms of the value. So hopefully this shows why I wanted to separate out complex numbers: they need special handling, and now they get it.

Pre-release of LaTeX for 2022-06-01 ready for testing

We submitted the latest pre-release version for the 2022-06-01 LaTeX kernel to CTAN recently. It should have made its way into TeX Live (both 2021 and the 2022 pre-test) for everyone by now, so it’s ready for user to try.

It already contains most updates to the LaTeX format that will become part of the standard in June; thus testing the them now will help identifying packages that need upgrading and finding any bugs lurking before the June release hits the streets; see below for how to do this in a safe way.

The highlights are briefly discussed below, further details plus smaller bug fixes and improvements not covered here can be found in the draft version of the LaTeX2e News Issue 35 newsletter.

New features in the kernel (highlights)

For users

One of the most significant changes in the code is one that users (hopefully) won’t notice: the definition of UTF-8 characters in pdfTeX. We have made these engine-protected, which should make processing them in expl3 a lot easier. The way the change has been set up means we don’t expect users to actually see a difference, but we do want to hear about how it is working. So get your complicated accents out and try them all over the place with pdfTeX. (LuaTeX and XeTeX users won’t even need to worry.) One thing that goes with this change is that we have updated the definition of \MakeUppercase and \MakeLowercase, so they use Unicode-aware expl3 code ‘behind the scenes’. Again, this should be transparent to users, but it would be good to hear how it works in the wild.

More visible are a small set of new commands we are adding in this pre-release. We are moving \fpeval and \inteval from the xfp package directly into the kernel. We are also adding \ExpandArgs and \UseName, ideas again taken from expl3. These commands allow control of expansion, so you can do a range of basic expansion tasks in document commands, without needing TeX programming or using expl3. For example, you can now do

\NewDocumentCommand\newcopyedit{mO{red}}
  {\newcounter{todo#1}%
   \ExpandArgs{c}\NewDocumentCommand{#1}{s m}%
     {\stepcounter{todo#1}%
      \IfBooleanTF {##1}%
         {\todo[color=#2!10]%
            {\UseName{thetodo#1}: ##2}}%
         {\todo[inline,color=#2!10]%
            {\UseName{thetodo#1}: ##2}}%
     }%
  }

which can create a document command by name: something people have been asking for many years.

One more addition from expl3 ideas is \IfBlankTF: this can test if it has been given an entirely blank argument. Here, blank means empty or just spaces: this comes up surprisingly often.

For package authors

Package authors might well choose to use the features described above. There is though one big change aimed squarely at packages: keyval-based option handling. We have introduced a new set of commands, \DeclareKeys, \ProcessKeyOptions and \SetKeys, which can be used to create keyvals and to use them as package options. \DeclareKeys uses the same approach as the expl3 function \keys_define:nn to create keys: each key has one or more ‘properties’ which control how it behaves. We have provided a small number of common properties at this stage, for storing key values in a macro, for setting a switch and for executing some code. We have also provided a method to define the usage of keys: whether they are only available at package loading time, in the preamble or can also be used in the document body.

\DeclareKeys
  {
    draft.if    = @mypkg@draft      ,
    draft.usage = preamble          ,
    name.store  = \@mypkg@name      ,
    name.usage  = load              ,
    command.code = \showtokens{#1}
  }

Package options can then be processed using \ProcessKeyOptions, which will set keys defined by \DeclareKeys. Keys can also be set in the document body using \SetKeys. All of these new commands take an optional argument to define the key family: the namespace for the keys. This is by default the name of the current package file.

More advanced key types can be created directly using expl3 (l3keys): the keys created by \DefineKeys are standard expl3 keys.

Unlike traditional package options, loading a package using \ProcessKeyOptions multiple times with different options will not lead to a clash error. Instead, the options will simply be passed to the same key handler. This means that the package author can control how repeatedly setting the same keys is handled.

\DocumentMetadata

There is one more addition to the kernel for use at the top of the document: \DocumentMetadata. It is the trigger to tell LaTeX that the current document is new/modern document that should use concepts not available in traditional LaTeX2e documents, for example, everything developed for the PDF tagging project.

This new command has to come first in a LaTeX document, before \documentclass. It is used, as the name suggests, to set metadata about the entire document, but while the PDF tagging project is being worked on, it is also used to enable new code from this project (see the discussion of latex-lab below).

Even if used with an empty argument, it will currently already show some effect, by loading the new pdfmanagement that offers a reliable and consistent interfaces for packages (such as hyperref, media9, etc.) that need to set or query PDF resources, so that they can coexist without overwriting their settings in random ways.

The hyperref package, for example, will switch to a new driver with extended possibilities, if the \DocumentMetadata declaration was used, you can see this with the following simple document, that does shows the new default link colors of the new driver.

\DocumentMetadata{}

\documentclass{article}
\usepackage{hyperref}

\begin{document}
\tableofcontents
\section{A link}  \url{https://www.latex-project.org}
\end{document}

The LaTeX-lab bundle

This is a new space to explore ideas that we think may get added to LaTeX. These experimental ideas are only activated if the right key is present in the argument to \DocumentMetadata, i.e., they do not affect users who do not wish to experiment with new features. For example, the key testphase can be used to enable code that has been developed for the PDF tagging project. We currently are in testphase II of the tagging project, and that can be activated using

\DocumentMetadata{testphase = phase-II}

This then loads tagpdf and additional support code from latex-lab and produces documents that have paragraph text and footnotes tagged; further document elements, e.g., headings and lists will follow soon as part of this phase.

The latex-lab space may also hold code that we are in the process of moving to the kernel, but that we first want to tests without the danger of disruption, for example, at the moment it hosts the new management code for independent marks, which will either in June of by the end of the year move to the format.

It is possible that some ideas from the lab will be dropped or modified: anyone using them should be mindful of that. However, we expect that most will eventually move to the kernel. Tagging will always require \DocumentMetadata to be present, but over time the need to activate it with the testphase key will be removed.

Outlook

We expect to produce another pre-release around the end of April, which will give us time to finish the release by June. Please help with the testing

Processing your documents with the pre-release is straightforward. All you have to do is to replace the invocation command by appending -dev to the executable, e.g., on the command line you would run

• pdflatex-dev myfile or
• lualatex-dev myfile or
• xelatex-dev myfile

instead of using pdflatex, lualatex or xelatex. If you use an integrated editing environment, then it depends on the system how to configure it to use an alternative format; but in any case the necessary modification should be straightforward.

Enjoy — Joseph & Frank

Neben der Nutzung der scrlttr2 Klasse gibt es in aktuelleren KOMA-Script Versionen auch die Möglichkeit, das scrletter-Paket zu nutzen. Hier ein Beispiel:

\documentclass[12pt,ngerman]{scrartcl}

\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{booktabs}
\usepackage{babel}
\usepackage{graphicx}
\usepackage{csquotes}
\usepackage{paralist}
\usepackage{xcolor}
\usepackage{palatino}
\usepackage{blindtext}
\usepackage{scrletter}

\setkomavar{fromname}{Max Mustermann}
\setkomavar{fromemail}{Max@Mustermann.de}

\setkomavar{fromaddress}{Musterweg 221, 12345 Musterstadt}

\setkomavar{firstfoot}{\usekomavar{fromemail}}


\begin{document}
\begin{letter}{Maria Mustermann \\ Mustergasse 1 \\ 12346 Musterstadt}

\opening{Hallo Maria,}

\blindtext[2]

\closing{Mit freundlichen Grüßen}

\end{letter}
\end{document}

Uwe

Uwe 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 here Spenden für die Dingfabrik.

More Posts - Website

Robin Fairbairns (1947 - 2022)

We are sad to report that our longtime friend, team member, and LaTeX contributor Robin Fairbairns died 25th February 2022, after a long period of ill health. Much missed husband of Linda, former husband and friend of Josy, father of Chloe and Sam, stepfather of Chloe and Lydia.

The Funeral will be on 30th March 2022.

Robin was instrumental in bringing the UK TeX archive to Cambridge, and setting up the CTAN TeX archive network in 1992, of which Cambridge, DANTE and SHSU were the three original hosts. The UK CTAN host was managed by Robin until his retirement in 2014. Robin wrote or maintained many well-used LaTeX packages that are on CTAN.

He also regularly served on the UKTUG Committee, and for many years developed and maintained the “UKTUG FAQ” archive of Questions and Answers on TeX related subjects. The FAQ is now maintained at https://texfaq.org but the majority of the text still reflects Robin’s original work.

Robin was a tireless member of the community who helped many people for many years with his kind, friendly, and patient approach. He clearly looked to improve the TeX ecosystem and worked hard to leave it in a better place after his time was up. He certainly succeeded in that.

With sadness

— The LaTeX Team

I’ve now done 49 (!) minor releases of siunitx on the v3.0.x branch. These have addressed quite a few minor bugs: I expected to have to do a bit of work since the shift from v2 was quite major.

Things are now settling down: the open issues I’ve had recently are mainly on the border of feature requests, and there don’t seem to be additional changes I’ve introduced by accident. With the TeX Live freeze coming up, now looks like an excellent time to turn my thoughts to siunitx v3.1. The plan there is to deal with two areas:

• Small requests that are clearly additions not bugs, so need API extensions but are easy/low risk
• Pick off one of the bigger requests, probably either multi-part uncertainties or parsing ‘free form’ units, or both if they are sufficiently straight-forward

Of course, that doesn’t rule out further bugs to be fixes in the v3.0 branch: I will continue to fix things that come up there.

Depending on how the big issues go, I might manage a v3.1 release in the summer (June-August).

LaTeX Graphics Companion 2ed is back in print

The LaTeX Graphics Companion 2nd edition, formerly publish by Addision-Wesely in the “Tools and Techniques for Computer Typesetting” series, went out of print a while ago. I’m happy to announce that this has now changed again. Lehmanns Media has picked up the book and produced an affordable reprint, both as printed softcover book and also as a DRM-free PDF ebook version:

• LaTeX Graphics Companion (softcover), ISBN 978-3-96543-303-8
• LaTeX Graphics Companion (ebook), ISBN 978-3-96543-299-4

Update 2022-03-08 (International ordering)

The book should be available from all major bookstores or online ebook providers. The above links point to the Lehmanns website (which only offers pages in the German language). Internationally, the book can be ordered through Amazon and the like and you find the ebook on Google Play or ciando and perhaps on others.

Happy LaTeXing — Frank

Dienstag abend hat die LaTeX Community Twitter erfolgreich durchgespielt: es wurde das Level erreicht, dass LaTeX in Deutschland auf Twitter trendet, den Abend lang. Und zwar in der korrekten Schreibweise, wichtig. Keine andere Sache.

Was ist passiert? Wir haben uns rege über LaTeX unterhalten, dann hat noch Anna eine Umfrage gestartet, was man für eine Doktorarbeit verwenden sollte (Spoiler: LaTeX) und es gab viele Kommentare und am Ende trendete LaTeX auf Twitter und es waren sehr viele Menschen irritiert – besonders die, welche das anklickten, doch nicht in Deutschland verortet wurden und Twitter zeigte ihnen was anderes…

Hier ein paar Screenshots, weil man sieht es ja nicht alle Tage und es scrollt weg…

Ich habe das etwas befeuert, sorry falls zuviele Tweets/Retweets ankamen, Likes sowieso… es war mal ein anderer Abend.

Auf Twitter bin ich als LaTeX.org unterwegs alias @TeXgallery, der Name kommt daher, weil ich dort 2011 angefangen habe mit TikZ-Bildern, Galerie. Wenn man so ein Profil anklickt, sieht man Tabs mit Tweets/Retweets (Blogposts, News, Links), Tweets und Antworten (Kommentare und Dialoge), Medien (Bilder) und Gefällt mir was in meinem Fall oft Zustimmung oder Bookmarken ist, was man vllt. nicht über den Hashtag #TeXLaTeX findet, den eher die Langzeit-User kennen.

Gestern war nur Spielerei, vielleicht. Zeigt aber, dass sich viele Menschen über LaTeX unterhalten. Ich war zu oft täglich auf Twitter, um all den Nachrichten zu folgen, von Corona-Pandemie bis zum Russland-Krieg gegen die Ukraine und die Atomkrieg-Angst. Gestern einige Stunden sicher und gut auf Twitter gefühlt in der LaTeX-Bubble.

Photo by Alexander Shatov on Unsplash

Hier ein Beispiel für das XCharter Paket, das einen passenden Mathe-Font für die Charter bereitstellt.

%!TEX TS-program = LuaLaTeX
\documentclass[12pt,ngerman]{scrartcl}

\usepackage{fontspec}
\usepackage{babel}
\usepackage{unicode-math}
\setmathfont{XCharter-Math.otf} % Call by file name or
\setmathfont{XCharter Math} % Call by font name

\setmainfont{XCharter}
\setsansfont{Cabin}[Scale=MatchLowercase] % sf
\setmonofont{Inconsolatazi4}[Scale=MatchLowercase] % tt

\usepackage{blindtext}

\begin{document}

\blindtext

\begin{equation}
\int_{x=1}^{\infty} -\frac{p}{2} \pm \sqrt{ \left(\frac{p}{2}  \right)^2 -q   } 
\end{equation}

\blindtext

\end{document}

Uwe

Uwe 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 here Spenden für die Dingfabrik.

More Posts - Website

LaTeX Graphics Companion 2ed is back in print

The LaTeX Graphics Companion 2nd edition, formerly publish by Addision-Wesely in the “Tools and Techniques for Computer Typesetting” series, went out of print a while ago. I’m happy to announce that this has now changed again. Lehmanns Media has picked up the book and produced an affordable reprint, both as printed softcover book and also as a PDF ebook version:

• LaTeX Graphics Companion (softcover), ISBN 978-3-96543-303-8
• LaTeX Graphics Companion (ebook), ISBN 978-3-96543-299-4

The book should be available from all major bookstores, the ebook version probably only from Lehmanns directly.

Happy LaTeXing — Frank

That’s an English translation a German blog post that you can find here: LaTeX.net/verein.

I’d like to support promoting becoming a new member of DANTE e.V. because I wish to see more LaTeX friends here.

February 8, 2022: More than 10 books available.

Why should I become a DANTE member?

You would be part of a big community of LaTeX enthusiasts. We love that typesetting system that we support by our membership. Here, in addition to LaTeX users there are many active supporters. Some write books and articles, some maintain servers, some develop and distribute LaTeX software or give trainings.

For example, I maintain several LaTeX internet forums in German, English and French, LaTeX online compiler, archive server, documentation server, FAQ pages, LaTeX graphic galleries and sites of bloggers; you can find a long list at LaTeX.net/about. DANTE sponsors the hardware.

As a member you get to know many things behind the scenes of the LaTeX world in the member journal, on the mailing list, or at (online) meetings.

Which book would I get?

It’s my personal offer, so I can just offer one of my books.

• The LaTeX Beginner’s Guide of 2021 (freshly revised second edition) – you can find all details, code examples and reviews on LaTeXguide.org. On amazon it would be 32,08 € for the printed version and 17,97 € for the ebook.
• The LaTeX Cookbook of 2015, details, code examples and reviews are on LaTeX-Cookbook.net. On amazon it is available for 43,85 € in the printed version and for 24,71 € as an ebook.

Here, we talk about the ebook.

How can I receive the book?

I would like to give you the book as a properly licensed ebook in a way that’s acceptable for the publisher. You will get an account at the Packt Publishing website registered to your name and your email address. That contains the book with download options and the invoice. You can get it as PDF, EPUB, MOBI, or Kindle version on your kindle reader or on your smartphone with kindle app (works fine on a smartphone).

How can I do this?

If you like LaTeX and you would like to join DANTE, great! Write me an email to stefan@latex.org and tell me which one of the books you like, I will reserve it for you. Then register at www.dante.de/dante-e-v/mitglied-werden.

I will ask DANTE e.V. if you are a member, your agreement for this and for allowing me to make you a Packt Publishing website account is required here, and by joining this plan you agree with it.

Membership fees are on the registration page, such as 15 € (pupils), 20 € (students, retirees), otherwise the regular fee is 40 € per person. So, if you are a student, the saved money for the book is close to the membership fee.

There are more than 10 book copies available. I will write here when it gets exhausted. Otherwise it’s ongoing and you could expect a book. Of course it’s a personal offer by me and not binding, I’ll try my best.

If I’m already a member, can I still get a book for free?

I’m pleased that you are interested, just write me to stefan@latex.org. Perhaps I got another copy just for you.

What else?

Then, as you are in email conversation with me, you may ask me what you would like to know – how is book writing, how is publishing, how do web servers work and forum and what makes an online LaTeX compiler work, what do we do at online meetings, and more.

Let me know!

An English translation of this post is here: LaTeX.net/members.

Da ich mir mehr LaTeX-Freunde für unseren Verein DANTE e.V. wünsche, möchte ich die Werbung von Neumitgliedern mit einem LaTeX-Buch unterstützen.

8. Februar 2022: Mehr als 10 Bücher verfügbar.

Warum DANTE-Mitglied werden?

Du wärst im Kreis vieler LaTeX-Begeisterter. Uns alle eint die Begeisterung für dieses freie Satzsystem, die wir über die Mitgliedschaft unterstützen. Neben den LaTeX-Anwendern gibt es viele, die LaTeX auch aktiv fördern. Manche schreiben Bücher und Artikel dazu, betreuen die Vereins-Server, entwickeln und verteilen LaTeX-Software oder geben Schulungen.

Ich zum Beispiel betreibe mehrere LaTeX-Internet-Foren in deutsch, englisch und französisch, LaTeX-Online-Compiler, Archiv-Server, Dokumente-Server, FAQ-Seiten, LaTeX-Grafik-Galerien und Seiten von LaTeX-Bloggern; die fast komplette Liste findest Du auf LaTeX.net/about. DANTE finanziert dabei die Hardware.

Als Mitglied erfährt man vieles von hinter dem Vorhang der LaTeX-Welt in der Mitgliederzeitschrift und auf der Vereins-Mailing-Liste oder begegnet sich auf (online) Tagungen.

Welches Buch würde ich bekommen?

Es ist meine eigene persönliche Werbe-Aktion, daher kann ich nur eines meiner eigenen, in englisch publizierten, Bücher anbieten.

• Der LaTeX Beginner’s Guide, ein Einsteigerbuch von 2021 (frisch überarbeitete 2. Auflage) – alle Details dazu, Codebeispiele sowie Buch-Kritiken findest Du auf LaTeXguide.org. Auf amazon wäre es für 32,08 € in gedruckter Version und als Ebook für 17,97 € zu haben.
• Das LaTeX Cookbook, eine Vielfalt von Rezepten für LaTeX-Dokumente von 2015, Details, Code-Galerie und Buch-Kritiken sind auf LaTeX-Cookbook.net. Auf amazon findet man es für 43,85 € in gedruckter Version für und 24,71 € als Ebook.

Bei dieser Aktion handelt es sich um das Ebook.

Wie würde ich das Buch bekommen?

Dir als Neumitglied möchte ich eins dieser Bücher schenken, als normal lizensiertes Ebook. Dazu erhältst Du von mir einen Account beim Verlag Packt Publishing, auf Deinen Namen und Deine Email-Adresse registriert, mit dem Buch samt Rechnungsbeleg darin. Dort kannst Du es als PDF oder im EPUB oder MOBI Format herunterladen oder als Kindle-Version auf Deinen Kindle-Reader schicken bzw. Dein Telefon oder Tablet mit Kindle-App (funktioniert prima auf dem Smartphone).

Wie nehme ich an der Aktion teil?

Wenn Du LaTeX magst und dem Verein beitreten möchtest, super! Schreib mir einfach an stefan@latex.org mit Deinem Buchwunsch, ich reserviere es dann für Dich. Dann registriere Dich auf www.dante.de/dante-e-v/mitglied-werden.

Ich frage dann bei DANTE e.V. nach deiner Mitgliedschaft, Dein Einverständnis für diese Abfrage sowie für die Buch Account-Erstellung auf Deinen Namen ist für die Aktion erforderlich, und durch Deine Teilnahme stimmst Du dem zu.

Die Mitgliedsbeträge variieren von 15 € (Schüler), 20 € (Studierende, Rentner), sonst 40 € je Person. Bist Du also beispielsweise ein Student, dann entspricht der Mitgliedsbeitrag fast dem am Buch gesparten Beitrag.

Es sind jeweils mehr als 10 Exemplare der Bücher vorhanden. Wenn sie (fast) alle weg sind, dann informiere ich darüber zuerst hier auf dieser Seite. Ansonsten läuft sie und Du kannst ein Buch erwarten. Natürlich ist es als persönliche Verschenk-Aktion unverbindlich und rein in meinem Ermessen, wie ich es mache und schaffe.

Kann ich als aktuelles Vereinsmitglied auch ein Buch kostenfrei bekommen?

Ich freue mich über Dein Interesse! Schreib mir gern an stefan@latex.org. Eventuell habe ich ja noch ein weiteres übrig.

Was noch?

Da Du dann in email-Kontakt mit mir stehst, kannst Du mich auch gern fragen, was Dich interessiert – wie das ist ist mit Bücherschreiben und Verlag, wie funktionieren Webserver, Foren, und Online-Compiler, was macht man so auf (online) Tagungen, und mehr.

Melde Dich gern!

Heute, am Donnerstag, 13. Januar 2022, gibt es den ersten Berliner LaTeX-Stammtisch des Jahres 2022, um 19 Uhr.

Nur für Berliner? Weiß nicht, hab ich gerade auf Twitter gefragt.

Weil es ist ja online mit jitsi-meet auf dieser Adresse:

https://meet.ffmuc.net/LaTeXStammtischBerlin

Keine besondere Tagesordnung. Ob man da mal reinschaut? Könnte interessant sein! War eh zu lange im Homeoffice. Wer meint was auf Twitter?

Photo by Drew Beamer on Unsplash

In the TeX world, the name Stefan Kottwitz is best known for the websites and forums he runs, but Stefan is not just a server admin but also a book author. The first edition of his LaTeX beginners book was published in 2011, followed by the “LaTeX Cookbook” in 2015, now the second edition of the beginners book “LaTeX Beginners Guide” is available.

The book is published by Packt, who kindly provided me with a copy of the book. As I had to prepare several LaTeX courses I was eager to have a closer look at it.

On a little more than 300 pages Stefan introduces the different aspects of LaTeX. On 25 pages the history of TeX and LaTeX is briefly outlined as well as the installation of TeX Live and the use of Overleaf. The second chapter is on how to format text. I like that this chapter already shows how to create your own commands as I also do this in my courses to show the participants how easy it is to use more complex markup with self-defined commands.

Chapter 3 shows how to set page formats and type area, followed by an explanation of the various list types in Chapter 4. Chapters 5 and 6 describe the typesetting of figures and tables, respectively, followed by cross-references in Chapter 7.

Chapter 8 shows how to customize tables of contents and create an index. In addition, Stefan discusses typesetting bibliographies with the standard bibliography environment and BibTeX in this chapter. BibLaTeX is unfortunately left out at this point, but Stefan describes it in his LaTeX Cookbook.

Chapter 9 is devoted to mathematics, covering all the constructs a student might encounter even in a STEM subject. Chapter 10 goes into the various fonts that can be used in pdfLaTeX, and also shows how any system fonts can be used with xeLaTeX or luaLaTeX. Chapter 11 shows in detail how to split longer documents into separate parts with \input and \include.

Chapter 13 is highly relevant especially for LaTeX newbies, as it shows how to narrow down and fix problems in case of errors.

The book ends with a detailed description of web forums and sites where one can get support and also introduces user groups like TUG and Dante e.V.. The website for the book can be found at latexguide.org. There you can find the FAQ for the book as well as the source code with online compilation.

In summary I can say that I liked the book of Stefan very much and I will recommend it also in my courses. Together with the LaTeX Cookbook, which describes not only Biblatex but also the creation of graphics using LaTeX, it offers a good introduction to LaTeX.

Antioch Sanders told us on LaTeX.org about his new project that he called extexify. That’s a browser extension for finding LaTeX symbols by drawing them with mouse or finger on the display. It is inspired by detexify, but works integrated in the Overleaf online LaTeX editor.

It is available as Chrome extension (beta version) and a firefox extension will come soon.

It tested it. The installation from the Chrome web store was straightforward, and when I opened Overleaf I noticed the extexify button in the top menu:

When I clicked it, a window opened where I could click and draw with the mouse. Below my hand-drawing I got LaTeX command suggestions for the symbol. While my drawing was so bad that I hardly new if it was a one of the letters phi, rho, or P, extexify suggested all of then and even a blackboard Q (double-stroke, mathds) – I had to think a second but also that one comes close.

I chose first suggestion and clicked the bottom left button – voila, the code \varphi was inserted into my code:

I tried other symbols and it worked fine. The author explained how he created the extension and how worked on the symbol recognizer, based on the detexify training data set. If you are curious how it works, follow the links.

extexify is available on Github. There you can make suggestions for improvements. Just be aware that it’s a public beta version, so not officially completed yet. I don’t even see a licensing information yet.

If you like it, you can show feedback by adding a star on Github and by rating in the Chrome web store.

log4j vulnerability: LaTeX is not affected!

We are seeing more and more requests asking us whether LaTeX needs a patch because of the log4j vulnerability, when the necessary patch is planned and ready, etc. Rather than to explain each time (which I did more than a dozen times by now) why nothing needs to be done at our end, I decided to post it here, so that I can refer to that statement.

Upfront I would like to apologize to any LaTeX user for the noise, because if you know what LaTeX is (a macro package running on top of the TeX program), then you are well aware that such questions are ill formed. But most people being charged to check all software in use in their organization do not know each and every piece of software and for them LaTeX is just a program that may or may not use log4j.

Well, LaTeX is not a program, it is input for a program (namely TeX or one of its variants) so the question has to be: is any of the TeX programs that make use of the LaTeX source as input vulnerable to the log4j issue?

The answer is fortunately a clear NO and the official statement for this from the TeX Users Group organization (for the TeXLive and MikTeX distributions) can be found here:

• TUG’s statement on the log4j vulnerability

If you talk to people who are searching for an answer whether or not LaTeX (or rather TeX) is affected by log4j and if so what is being done about it, please refer them to TUG and that statement.

Happy and continuously safe LaTeXing — Frank

The third major release of siunitx was out in May, after the TeX Live 2021 DVD. That means it’s been picked up primarily by more active users: people who install TeX between the ‘fixed’ DVD releases (or who use MiKTeX). It also didn’t initially appear on Overleaf, as they take a while to test TeX Live images before making them public.

I’ve been making maintenance releases between May and now, and have reached v3.0.36, picking off small (or less small) issues I’d missed initially. At the same time, Overleaf now have a TeX Live 2021 image (currently featuring siunitx v3.0.23). So I now have an increasing number of ‘normal’ users: people who don’t want to deal with testing, and just want their documents to work.

What I notice is that increased usage hasn’t raised any truly major issues. Yes, there have been corrections (see the ChangeLog for the detail), but they were mainly at the level of predictable issues: places that I’d not explored quite enough. I hope Overleaf will consider an in-place update to somewhere around the latest release: whilst the issues have been minor in the grand scheme, it would be good to get a reasonably bug-reduced version out there (I’m not claiming bug-free)!

So I’m seeing the release as in the end quite a big success: I’ve addressed the issues I knew about, got better testing, have cleaner interfaces and am already offering new features. My mind is therefore turning to v3.1: I have a list of issues to consider that I’d like to take for that release, plus I could pick off some others. I might of course not tackle all of these: I’m thinking starting over the Christmas period and looking to release in March/April 2022. By then of course we might be at v3.0.50, so it will also help to ‘reset’ the patch level!

I’ve been meaning for a little while to look properly at my Jeykll theme for the site and tidy it up: it was a bit basic. Prompted in part by Will Robertson, I decided that now is the moment.

I consulted with my favourite duck internet buddy, Paulo Cereda, and he pointed my to the rather flexible Hamilton theme. You’ll see I’m tweaking it a bit, so there will be minor changes over time, but I think it looks good: balances off between not being totally plain with the fact I have zero design ability!

Paulo himself doesn’t have a blog, but he’s part of the excellent Island of TeX, most famous for arara. Paulo tells me they don’t use Jekyll, but rather Zola, but that didn’t stop him helping me :)

The Fall 2021 LaTeX release is available

As we have announced previously, we have shifted the release dates for LaTeX slightly, to better align with the yearly release of TeX Live: a first release in May/June after TeX Live has updated and a second release around November.

The current release does not contain any major new modules, but is focused around consolidation and improvements of functionality introduced in previous releases. In the meantime we are working further on the future production of reliable tagged PDF output (see the article LaTeX Tagged PDF — A blueprint for a large project that describes the project we are engaged in), which will again take center stage in the Spring release 2022.

Hook management improvements

There have been some improvements of the hook management as a result of feedback from developers and our own experience applying the new functionality. This includes one breaking change in behavior (relevant only to package developers), for which we offer compatibility code for now. Thus nothing will break right now, but going forward the new method needs to be used, because at some point in the future the compatibility code will be taken out.

• Standardizing generic hook names;
• Rationalizing the behavior of \RemoveFromHook;
• Providing \ActivateGenericHook;
• Providing a command to clear “next” hook code before invocation;
• Properly clean up after a one-time hook.

New or improved commands

There are many enhancements and corrections that we documented in the ltnews article for this release (and a few very minor ones that only made it into the changes.txt file). The most important aspects from a user perspective are:

• Extending \ShowCommand to show commands defined with \NewDocumentCommand and friends;
• Extending \NewCommandCopy as well, to safely copy such commands to new names;
• Improving the math font family allocation to avoid running out of available math groups in complex documents. A number of math alphabets (controlled through the counter localmathalphabets) are now locally allocated and their math groups can be reused with different alphabets per formula;
• Adding \PackageNote and \PackageNoteOnLine to show notes that aren’t “warnings” on the terminal;
• Supporting an alt key with \includegraphics (anticipating future development);
• Providing a new \newcolumn command and an optional argument to \columnbreak for multicol;
• Altering the default for \tracinglostchars.

But read the whole ltnews article because there may be other gems that are useful for you.

Where to learn more …

The new features and most of the important bug fixes made in this release are documented in “LaTeX2e News Issue 34”. This document can be found on the LaTeX2e news page where you will also find release information for earlier LaTeX releases.

Happy LaTeXing — Frank

The final LaTeX pre-release for 2021-11-15 is available for testing

A few days ago we submitted the final pre-release of the LaTeX format to CTAN and by now it should be available to all users using MiKTeX or TeX Live (on any operating system).

Main features included in the final pre-release for 2021-11-15

The upcoming release does not contain any major new modules, but is focused around consolidation and improvements of functionality introduced in previous releases. There have been some improvements of the hook management as a result of feedback from developers and our own experience applying the new functionality. This includes one breaking change in behavior (relevant only to package developers), for which we offer compatibility code for now. Thus nothing will break right now, but going forward the new method needs to be used, because at some point in the future the compatibility code will be taken out.

The hook management improvements are

• Standardizing generic hook names;
• Rationalizing the behavior of \RemoveFromHook;
• Providing \ActivateGenericHook;
• Providing a command to clear “next” hook code before invocation;
• Properly clean up after a one-time hook.

Other notable improvements include

• Extending \ShowCommand to show commands defined with \NewDocumentCommand and friends;
• Extending \NewCommandCopy as well, to safely copy such commands to new names;
• Improving the math font family allocation to avoid running out of available math groups in complex documents. A number of math alphabets (controlled through the counter localmathalphabets) are now locally allocated and their math groups can be reused with different alphabets per formula;
• Adding \PackageNote and \PackageNoteOnLine to show notes that aren’t “warnings” on the terminal;
• Supporting an alt key with \includegraphics (anticipating future development);
• Providing a new \newcolumn command and an optional argument to \columnbreak for multicol;
• Altering the default for \tracinglostchars.

There are also a number of smaller enhancements and some bug fixes as usual. The details are discussed in the draft publication of “LaTeX2e News Issue 34”. A full list is given in the changes.txt files that are part of the distribution.

Outlook

We expect to ship the final release (with the same code base as this pre-release) as planned around mid November.

Please help with the testing

We are issuing this final pre-release now in the hope that you will help us by making sure that all the enhancements and fixes we have provided are safe and that they do not have any undesired side effects, so please help with the testing if you can.

This development format allows you to test the upcoming LaTeX release scheduled for 2021-11-15 with your documents or packages. Such testing is particularly important for package maintainers to verify that changes to the core LaTeX haven’t introduced incompatibilities with existing code. We try to identify any such problems beforehand but such an undertaking is necessarily incomplete, which is why we are asking for user testing.

Besides developers, we also ask ordinary users to try out the new release, because the more people that test the new format, the higher the chances that any hidden problems are identified before the final release hits the streets.

Processing your documents with the pre-release is straightforward. All you have to do is to replace the invocation command by appending -dev to the executable, e.g., on the command line you would run

pdflatex-dev myfile    or    lualatex-dev myfile    or    xelatex-dev myfile

instead of using pdflatex, lualatex or xelatex. If you use an integrated editing environment, then it depends on the system how to configure it to use an alternative format; but in any case the necessary modification should be straightforward.

Enjoy — Frank

The second LaTeX pre-release for 2021-11-15 is available for testing

A few days ago we submitted a new LaTeX development format to CTAN and by now it should be available to all users using MiKTeX or TeX Live (on any operating system).

Main features of the second pre-release for 2021-11-15

The first pre-release was just a copy of the main release for 2021-06-01 in order to avoid that people using the development release regularly get an old format.

The second pre-release now provides some improvements of the hook management as a result of feedback from developers and our own experience applying the new functionality. This includes one breaking change in behavior (relevant only to package developers), for which we offer compatibility code for now. Thus nothing will break right now, but going forward the new method needs to be used, because at some point in the future the compatibility code will be taken out.

Notable improvements already contained in the pre-release are

• Resolving some issues around the new hook functionality:
  • Providing \ActivateGenericHook;
  • Command to clear “next” hook code before invocation;
  • Cleanup after a one-time hook;
  • Changed the behavior of \RemoveFromHook;
  • Standardizing generic hook names;
• Other improvements:
  • \tracinglostchars got a new default
  • \PackageNote was added to show notes that aren’t “warnings” on the terminal
  • \ShowCommand got extended to show commands defined with ltcmd (former xparse)
  • \NewCommandCopy got extended as well to safely these commands to new names
  • alt key for \includegraphics (anticipating future development)

There are also a number of smaller enhancements and some bug fixes as usual. The more important ones are listed in the draft publication of “LaTeX2e News Issue 34”. A full list is given in the changes.txt files that are part of the distribution.

Improving the hook management further

The breaking change mentioned above involves the name of generic file hooks. They used a special naming convention in the past and we now changed them to use the same structure as all other generic hooks, that is, their “variable” part (i.e., the file or package name) is always in the second position. For example, to execute some code after the array package was loaded you now say

\AddToHook{package/array/after}{...code...}

just like you would set up code to be executed after each tabular environment with

\AddToHook{env/tabular/after}{...code...}

For now the old syntax package/after/array is still supported, thus packages making use of this functionality have time to adapt to the new convention once the main release is out and distributed.

Other improvements to the hook management (e.g., the functionality to have packages implement generic hooks) are discussed in LaTeX2e News Issue 34 and in the relevant kernel documentation.

Outlook

We expect to produce a third and final pre-release adding some more features and enhancements in late October.

Please help with the testing

We are issuing this second pre-release now in the hope that you will help us by making sure that all the enhancements and fixes we have provided are safe and that they do not have any undesired side effects, so please help with the testing if you can.

This development format allows you to test the upcoming LaTeX release scheduled for 2021-11-15 with your documents or packages. Such testing is particularly important for package maintainers to verify that changes to the core LaTeX haven’t introduced incompatibilities with existing code. We try to identify any such problems beforehand but such an undertaking is necessarily incomplete, which is why we are asking for user testing.

Besides developers, we also ask ordinary users to try out the new release, because the more people that test the new format, the higher the chances that any hidden problems are identified before the final release hits the streets.

Processing your documents with the pre-release is straightforward. All you have to do is to replace the invocation command by appending -dev to the executable, e.g., on the command line you would run

pdflatex-dev myfile    or    lualatex-dev myfile    or    xelatex-dev myfile

instead of using pdflatex, lualatex or xelatex. If you use an integrated editing environment, then it depends on the system how to configure it to use an alternative format; but in any case the necessary modification should be straightforward.

Enjoy — Frank

The following text is in German because it’s about the German language user group meeting 2021.

Im vergangenen Jahr sind leider beide DANTE-Tagungen wegen der Pandemie ausgefallen. Die Frühjahrstagung fand wegen der Kontaktbeschränkungen komplett online statt.

Auch die Herbsttagung wird virtuell stattfinden, über die Plattform „Online Schule Saarland“.

Das Programm, vom 17. bis 19. September 2021:

• Freitag, 17.9.: ab 19:30 Uhr Vorabendtreff
• Samstag,18.9.: ab 9 Uhr Begrüßung und Mitgliederversammlung , danach zwei Vorträge
  • Color, xcolor und l3color: Farben in LaTeX (Ulrike Fischer)
  • Futura PM – Eine geometrisch konstruierte Schriftart für (La)TeX (Philipp Müller)
• Sonntag, 19.9.: Stadtrundgang und Besuch historisches Museum

Siehe auch Programm und Tagungs-Seite.

An dieser Stelle auch ein Danke von mir an DANTE für die Unterstützung bei den Serverkosten dieser Webseite TeX-talk.net sowie der LaTeX-Foren TeXwelt.de, goLaTeX.de, LaTeX.org, TeXnique.fr, und weiteren Webseiten wie TeXfragen.de, LaTeX.net.br, TeXdoc.org, CTAN.net, TeXlive.net, TeX.my, TeXample.net, TikZ.net, pgfplots.net, TeXblog.net, mychemistry.eu, TeX.co, LaTeX.net und weiteren.

Photo by Amador Loureiro on Unsplash

In 2020, the Island of TeX introduced Docker images for easily reproducible builds as well as a semi-official response to the need for continuous integration. These images were among the first using vanilla TeX Live, providing the required tools for running software included in TeX Live – for example, Java Virtual Machine, Python, and so forth. Additionally, the island provides TeX Live releases from 2014 on and let the user decide whether they want to pull all the documentation and source files into their CI configuration.

With attention came the idea to more officially publish our images as texlive/texlive, which the island gladly did. Now IoT manages the releases at Docker Hub as well: https://hub.docker.com/r/texlive/texlive.

Docker Hub is the world’s largest repository of container images with an array of content sources including container community developers, open source projects and independent software vendors building and distributing their code in containers.

Apart from applications in continuous integration, the Docker images have lured the island into creating another tool based on them. TeXdoc online is the successor to TeXdoc.net (which now redirects).

This tool provides a RESTful API for texdoc. A REST ful API is a stateless interface to web applications responding to typical HTTP requests with uniform responses. Usually, JSON is used for the response format. Following this principle, this software responds to HTTP GET requests with JSON representing documentation-related objects. There are several endpoints you can access.

The front end of TeXdoc online is structured in a similar way to TeXdoc.net. The main feature is still searching for packages. Topics are handled differently, though. We use CTAN’s JSON API to fetch their topics and packages belonging to these topics. Any user visiting the landing page will be shown six random categories with a few packages each. If a category holds several packages, four of them are selected at random. Users have the option to show all topics and list the packages for any topic they are interested in. Also, each package entry can be automatically queried for documentation.

Deploying the software is straightforward. You can get an executable JAR file with all dependencies included that you can simply run using your local Java installation. Running the JAR bundle will open a local web server that can be accessed from your browser. As an alternative to running the JAR file, the island also provides a dockerized image. This image is based on IoT’s TeX Live images, which makes it quite large in terms of file size but also eliminates the need for a local TeX installation. Using Docker is the preferred solution for hosting your own instance of TeXdoc online.

The Docker image also provides daily updates. The container will update daily at midnight (container time) and thus stays up to date as long as
the current version of TeX Live is supported. The island’s continuous integration ensures that you can always pull the latest tag and receive the latest and greatest TeX documentation, which when pulled and run will update itself.

To ease deployment, IoT provides a ready-made configuration for Docker Compose, an orchestration tool for Docker containers. It uses the Caddy web server to provide automatic HTTPS with local certificates or, on public domains, Let’s Encrypt certificates.

After finishing TeXdoc online to a production-ready degree, the island turned to the development of another handy tool, Albatross. This command line tool, with a silly yet adorable name, solves a very common problem: finding system fonts that provide a certain glyph. Users may provide the glyphs themselves or their corresponding Unicode code points in hexadecimal notation.

IoT also migrated checkcites, a tool for checking missing or unused references, from Paulo’s personal repository to the island. The team also decided to rewrite it from Lua to Kotlin — this is still a work in progress. And the island is going from a monolithic implementation to a modular one, which is also a work in progress.

In 2020, IoT finished version 5 of arara, a major rewrite from Java to Kotlin, mainly working on features from user feedback, especially directory support and the processing of multiple files. The team got hooked by the idea of aligning release schedules of arara with TeX Live releases enabling IoT to make (small) breaking changes more often. So the island had big plans and started to work on version 6 right after releasing version 5. As with checkcites, the team walked the extra mile and arara went from a monolithic implementation to a modular one, plus an enhanced feature set and optimized workflow.

In version 5, the implementation had everything contained in one big block. In version 6, IoT made a split between an API, a core implementation, the engine and the CLI application to separate concerns. This was the first step in the direction of splitting out components that are bound to one platform. Aditionally, the team hopes to enable other people to develop their own tools based on the arara libraries if they wish to. With multiple library components this should be easy. The developers of the TeXify IDEA plugin expressed their interest in this to integrate proper arara support in TeXify.

For version 7, the team wants to take larger steps towards platform-independence. Hence, IoT will make use of Kotlin/Multiplatform (MPP) to use a single codebase for all target platforms. Some components will have to be rewritten, some need different interfaces for different platforms but in the end, the team hopes to provide an even more multitalented tool.

Up to now, arara has been developed as a file-based build tool. The tool does not track dependencies nor does it manage projects. You throw a file at it and it makes the best out of it. The team is evaluating support for projects and dependencies. Other feature candidates include cleaner logs and granularity switchs, new DSL-based rules and configurations, and better integration with existing workflows.

The team has many plans and hopes to realize as much as possible. The island is a vibrant environment for the development of TeX-related tools; IoT wants to enhance the user experience, from newbie to expert, and promote use and diffusion of modern methodologies and technologies. If you are interested in helping the island develop ideas or even implementing some code, visas for the island are free and easy to get, so feel free to reach out.

Zum Thema Pocketmod hatte ich schon früher etwas geschrieben (https://www.uweziegenhagen.de/?p=1294), hier nun ein Template für ein TODO-Listen Pocket in DIN A3.

Das fertige PDF sieht dann so aus: PocketMod_for_A3

\documentclass[21pt]{scrartcl}
\usepackage[left=2cm,right=2cm, top=2cm,bottom=2cm,a3paper]{geometry}

\usepackage{forloop}
\setlength{\parindent}{0pt}
\usepackage{tikz}

\newcounter{ct} 
\usepackage{pgfpages}
 
\def\pgfpageoptionheight{\the\paperwidth} % landscaped by default
\def\pgfpageoptionwidth{\the\paperheight}
\def\pgfpageoptionborder{0pt}
\def\pgfpageoptionfirstshipout{1}
 
\pgfpagesphysicalpageoptions{%
    logical pages=8,%
    physical height=\pgfpageoptionheight,%
    physical width=\pgfpageoptionwidth,%
    current logical shipout=\pgfpageoptionfirstshipout%
}
 
    \pgfpageslogicalpageoptions{1}{%
      border shrink=\pgfpageoptionborder,%
      resized width=.25\pgfphysicalwidth,%
      border code=\pgfusepath{stroke},%
      resized height=0.5\pgfphysicalheight,%
      center=\pgfpoint{.875\pgfphysicalwidth}{.75\pgfphysicalheight}%
    }%
    \pgfpageslogicalpageoptions{2}
    {%
      border shrink=\pgfpageoptionborder,%
      resized width=.25\pgfphysicalwidth,%
      border code=\pgfusepath{stroke},%
      rotation=180,%      
      resized height=0.5\pgfphysicalheight,%
      center=\pgfpoint{.875\pgfphysicalwidth}{.25\pgfphysicalheight}%
    }%
 
    \pgfpageslogicalpageoptions{3}
    {%
      border shrink=\pgfpageoptionborder,%
      resized width=.25\pgfphysicalwidth,%
      border code=\pgfusepath{stroke},%
      rotation=180,%      
      resized height=0.5\pgfphysicalheight,%
      center=\pgfpoint{.625\pgfphysicalwidth}{.25\pgfphysicalheight}%
    }%
    \pgfpageslogicalpageoptions{4}
    {%
      border shrink=\pgfpageoptionborder,%
      resized width=.25\pgfphysicalwidth,%
      border code=\pgfusepath{stroke},%
      rotation=180,%      
      resized height=0.5\pgfphysicalheight,%
      center=\pgfpoint{.375\pgfphysicalwidth}{.25\pgfphysicalheight}%
    }%
 
    \pgfpageslogicalpageoptions{5}
    {%
      border shrink=\pgfpageoptionborder,%
      resized width=.25\pgfphysicalwidth,%
      border code=\pgfusepath{stroke},%
      rotation=180,%
      resized height=0.5\pgfphysicalheight,%
      center=\pgfpoint{.125\pgfphysicalwidth}{.25\pgfphysicalheight}%
    }%
    \pgfpageslogicalpageoptions{6}
    {%
      border shrink=\pgfpageoptionborder,%
      resized width=.25\pgfphysicalwidth,%
      border code=\pgfusepath{stroke},%
      resized height=0.5\pgfphysicalheight,%
      center=\pgfpoint{.125\pgfphysicalwidth}{.75\pgfphysicalheight}%
    }%
 
    \pgfpageslogicalpageoptions{7}
    {%
      border shrink=\pgfpageoptionborder,%
      resized width=.25\pgfphysicalwidth,%
      border code=\pgfusepath{stroke},%
      resized height=0.5\pgfphysicalheight,%
      center=\pgfpoint{.375\pgfphysicalwidth}{.75\pgfphysicalheight}%
    }%
    \pgfpageslogicalpageoptions{8}
    {%
      border shrink=\pgfpageoptionborder,%
      resized width=.25\pgfphysicalwidth,%
      border code=\pgfusepath{stroke},%
      resized height=0.5\pgfphysicalheight,%
      center=\pgfpoint{.625\pgfphysicalwidth}{.75\pgfphysicalheight}%
    }%
 

\begin{document}%

\forloop{ct}{1}{\value{ct} < 9}{%
\begin{tikzpicture}
\foreach \i in {0,...,-17}{%
\draw[very thick] (0,\i*2) -- ++(0,1.5) -- ++(1.5,0) -- ++(0,-1.5)--cycle; 
\draw[very thick] (2.5,\i*2) -- (22,\i*2);
\draw[very thick] (23,\i*2) -- ++(0,1.5) -- ++(1.5,0) -- ++(0,-1.5)--cycle; 
}
\end{tikzpicture}
\clearpage
}

\end{document}

Uwe

Uwe 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 here Spenden für die Dingfabrik.

More Posts - Website

Usually, I keep my day job (as a university lecturer in chemistry) and my LaTeX work separate. Of course, I use LaTeX at work for things like lecture handouts, but most of the time the two areas don’t directly intersect.

So it was quite interesting to be talking yesterday at a chemistry conference (the ACS Fall 2021 Meeting) about siunitx. I’d been invited by Stuart Chalk to a session on units and data reuse: much more like metrology/computer science than my usual day-to-day wet chemistry!

It was good to see that many of the things I do in siunitx fit into wider efforts by people who do day-to-day work on units. The idea of logical mark-up for unit input, the ability to decompose units into parts and the realities of less-than-ideal input from users were all there. Hopefully, siunitx will help with the work being done by groups such as DRUM (Digital Representation of Units of Measure) to make information more computer-readable. I’ll also be looking at QUDT for inspiration about the real technical detail of the myriad of units in real use.

I also managed to get in a few comments about some LaTeX work that’s important for data reuse more widely: tagged PDFs and tex4ht. So it was a pretty productive use of an evening!

MacKichan Software, Inc. stopped it’s business on June 30, 2021. Their products Scientific WorkPlace (SWP), Scientific Word, and Scientific Notebook, that are based on LaTeX, will not be sold or supported anymore.

The future plan for Scientific Word is to become Open Source after removing non-free/non-open components.

Image by Theodore Norvell

StackExchange, bekannt als StackOverflow, ist an Prosus verkauft worden f체r 1,8 Milliarden Dollar. Das beinhaltet die TeX StackExchange Q&A Seite (TeX.SE). Prosus ist ein Technology-Investor und eine Holding Company die bereits Unternehmen wie Udemy, Codecadamy und Brainly (“Your 24/7 homework helper”) besitzt. Nach $153 Millionen Investor-Kapital, Einstellen eines fr체heren Investment-Bankers als Kopf, mehreren Entlassungs-Runden, Ausscheiden von Moderatoren, Effizienter-Werden duch Standardisieren der Sites, Aussteige-Spekulationen, war es nicht wirklich 체berraschend. Die offizielle Kommunikation und Joel Spolskys Bekanntmachung sagen “business as usual” und dass alles genauso weiterl채uft. Also, nix zu sehen hier.

Es gibt auch nichtkommerzielle (La)TeX Q&A Seiten und Foren, unterst체tzt durch TeX user groups und vor allem DANTE, wie: LaTeX.org, TeXwelt.de, TeXnique.fr, and goLaTeX.de.

The StackExchange network by Stack Overflow Inc., has been sold to Prosus for 1.8 billion dollars. That includes the TeX Stack Exchange Q&A site aka TeX.SE. Prosus is a technology investor and holding company that already owns some learning sites such as Udemy, Codecadamy, and Brainly (“Your 24/7 homework helper”). After $153 Million funding, hiring a former investment banker to lead the company, several round of layoffs, community moderators leaving, becoming more efficient by standardizing site designs, exiting rumours, it was not surprising. Official communication and Joel Spolskys announcement say “business as usual” and that it would operate in the same way. Like, nothing to see here.

There are also not-for-profit (La)TeX Q&A sites and forums, supported by TeX user groups and especially DANTE, such as: LaTeX.org, TeXwelt.de, TeXnique.fr, and goLaTeX.de.

The Spring 2021 LaTeX release is available

This year Spring in LaTeX’s counting is somewhat delayed, but this fits the weather—at least here in Germany were we had April weather throughout most of May. We plan to keep it this way in future releases: a first release in May/June and a second release around November as this better fits with the release cycle of the TeXLive distribution.

The focus of this release is to provide further important building blocks for the future production of reliable tagged PDF output (see the article LaTeX Tagged PDF — A blueprint for a large project that describes the project we are engaged in); these enhancements are discussed below.

Extending the hook concept to paragraphs

Largely triggered by the need for better control of paragraph text processing, in particular when producing tagged PDF output, we have changed LaTeX so that the kernel gains control both at the start and at the end of each paragraph. This is done in a manner that is (or should be) transparent to both packages and documents. We have also included four public hooks to enable adding code to paragraphs in a controlled manner. The documentation on this is available as ltpara-doc.pdf.

These hooks will enable us to automatically tag paragraphs and enables us to identify when paragraphs are broken across columns or pages, because those need special handling in tagged PDF.

Extending the hook concept to commands

With this release we extended the set of “generic” hooks to commands: in theory each document-level command has now two hooks cmd/<command>/before and cmd/<command>/after in which packages (or the user in the preamble) can add code using the hook management machinery.

If you know the etoolbox package, then you can think of them as being similar to the use of \preto and \appto from that package, but with the difference that if different packages try to do that, the added code chunks can be controlled and ordered as needed using the hook mechanism. The documentation for this functionality can be found in ltcmdhook-doc.pdf.

In practice, not all commands can accept such generic hooks: some (especially those that take optional arguments) will break if you try using an /after hook with them. However, many will and that allows us in the future to easily patch the many commands to enable tagged PDF without touching or updating package code.

A large number of other enhancements and corrections

There are many other enhancements and corrections that we documented in the ltnews article for this release (and a few very minor ones that only made it into the changes.txt file). The most important ones from a user perspective are:

• Further improvements of file name parsing; in particular we made the parsing much faster again (it got a little slow with the functional enhancements we introduced in the last releases)
• Better handling of font series and font shape changes
• Improved copy & paste from documents produced with pdfTeX

But read the whole ltnews article because there may be other gems that are useful for you.

Where to learn more …

The new features and most of the important bug fixes made in this release are documented in “LaTeX2e News Issue 33”. This document can be found on the LaTeX2e news page where you will also find release information for earlier LaTeX releases.

Happy LaTeXing — Frank

Nach einem kurzen Gespr채ch auf TeXnique.fr hat Patrick Bideault das coffeestains-Paket auf TikZ portiert. Das urspr체nglich von Hanno Rein in 2009 entworfene Paket erfuhr damit eine Modernisierung und l채uft einwandfrei mit pdfLaTeX, XeLaTeX, und LuaLaTeX auf TeX Live 2021. Damit steht einer weiteren breiten Anwendung in den Homeoffices dieser Welt nichts im Wege.

Ein Anwendungsbeispiel mit viel Kaffee:

\documentclass{article}
\usepackage[ngerman]{babel}
\usepackage{blindtext}
\usepackage{coffeestains}
\begin{document}
\coffeestainA{1}{1}{0}{6cm}{4cm}
\coffeestainB{0.8}{1}{-60}{-4cm}{4cm}
\coffeestainC{0.3}{1}{180}{0cm}{0cm}
\coffeestainD{0.5}{0.5}{100}{-1cm}{2cm}
\blinddocument
\end{document}

Die Syntax ist, verk체rzt: \coffeestain(A|B|C|D){Transparenz}{Skalierung}{Drehwinkel}{X-Offset}{Y-Offset}. Mehr steht in der Dokumentation, die auch mit viel Kaffee entstanden ist.

Wilhelm Haager hat im April 2021 das Paket worldflags veröffentlicht. Damit kann man Flaggen aller Nationen und einiger weiterer Gebiete und Organisationen in TikZ zeichnen, sowohl als TikZ-Bild als auch als pic-Baustein. Durch eine Vielzahl Optionen kann man Breite, Höhe, “Hängen”, Spiegel, Drehen und mehr einstellen. Die einfachste Nutzung ist geht schon z.B. mit

\worldflag{BR}

was eine brasilianische Flagge zeichnet:

Mit etwas mehr Arbeit anhand des Beispiels im Handbuch mit Fahnenstangen:

\documentclass[border=10pt]{standalone}
\usepackage{worldflags}
\begin{document}
\begin{tikzpicture}[x=1mm,y=1mm]
\def\w{30}\def\d{20}
\pgfdeclarehorizontalshading{flagpole}{30mm}{color(0mm)=(white);
  color(1mm)=(brown); color(2mm)=(black)}
\flagsdefault[width=15mm,hang=20]
\pic (fr) [country=FR,width=16mm,rotate=-\w] at (\d,0) {worldflag};
\pic (de) [country=DE,width=15mm,rotate=\w,turn=180] at (-\d,0) {worldflag};
\fill [shading=flagpole,shading angle=-\w,
       rotate around={-\w:(fr-nw)}](fr-nw)-|++(-2,-60)-|cycle;
\fill [shading=flagpole,shading angle=\w,
       rotate around={\w:(de-nw)}](de-nw)-|++(2,-60)-|cycle;
\node [rotate={50},below left  = 1.5cm and -0.6cm of de-nw] {\TeX welt.de};
\node [rotate={-50},below left  = 1.2cm and 0.9cm of fr-ne] {\TeX nique.fr};
\end{tikzpicture}
\end{document}

Die Flaggen wurden mithilfe der Konstruktions-Angaben von vexilla-mundi.com gezeichnet, einige komplexere Embleme wurden aus SVG-Daten von Wikipedia mittels Inkscape in TikZ-Code übersetzt.

Wie hier notiert, ist es ja total einfach, LaTeX als kompletten und aktuellen Compiler in Blogs online zu verwenden.

Während ich gerade ein 10 Jahre altes Buch überarbeite damit es aktualisiert wird, verwende ich pro Kapitel eine Blog-Seite, um die sich im Kapitel entwickelnden Codes auf einer einzigen Seite zu haben und mit einem Klick zu übersetzen und zusammen zu überarbeiten bis es final ist. Ich hab halt sonst keinen Editor, der 12 Code-Beispiele auf einer Seite hat und jeden Teil mit einem Klick übersetzt, und das eben auch mit dem Smartphone unterwegs.

Lustigerweise rutscht es in Feed-Aggregatoren wie planet.dante.de obwohl es als Draft gespeichert ist und eigentlich nicht öffentlich sichtbar sein sollte.

Daher, sorry für den noise auf dem DANTE Planeten für zumindest einen reingerutschten Beitrag, wo auch noch User-Testcode von einem Forum-Beitrag drin war. Eigentlich mache ich das sonst auf einer separaten Buch-Webseite, die allen Code direkt on-page compilierbar enthält, analog LaTeX-Cookbook.net.

Sehen wir uns demnächst mit der Buch-Webseite und mehr Inhalten.

With v3 of siunitx out, I am as expected getting quite a few questions about moving from v2. In the main, this is quite easy as there is a decent amount of compatibility code. Here, I’ll pick out a few cases where you might want some adjustments.

Working with Overleaf

One thing that people sometimes need is to work with the latest version but allow their input to work with the older version: that’s particularly true if you work with people using Overleaf, as it will be some time before they update to v3. You can of course just stick to the v2 interfaces, but if you’d prefer to have v3 if possible, then you will need to define \qty and \unit (and maybe others) conditionally. I’d recommend doing that using

\usepackage{siunitx}
\ifdefined\qty\else
  \ifdefined\NewCommandCopy
    \NewCommandCopy\qty\SI
  \else
    \NewDocumentCommand\qty{O{}mm}{\SI[#1]{#2}{#3}}
  \fi
\fi
\ifdefined\unit\else
  \ifdefined\NewCommandCopy
    \NewCommandCopy\unit\si
  \else
    \NewDocumentCommand\unit{O{}m}{\si[#1]{#2}}
  \fi
\fi

That then leaves options, but almost always these should be set in the preamble, so are a ‘one shot’. You can of course add to my tests above to know which version is in use, and set selectively.

Working with products or complex values

For people who’ve been using products or complex numbers in \SI in v2, one could use a similar approach to the above to ‘keep’ the functionality by setting it equivalent to the new \qtyproduct or \complexqty commands: of course, if you want both then you’ve got to make bigger changes. For example, to retain the ability to use products in \SI, you’d use

\usepackage{siunitx}
\ifdefined\qtyproduct\else
  \ifdefined\DeclareCommandCopy
    \DeclareCommandCopy\SI\qtyproduct
  \else
    \DeclareDocumentCommand\SI{O{}mm}{\qtyproduct[#1]{#2}{#3}}
  \fi
\fi

at the cost that the code is a bit slower than \qty for input without products. Complex values would be handed the same way, just changing the command you use as a ‘replacement’.

Using litres (liters)

In v2, \litre and \liter produced different output: that was not the best interface decision. So in v3 they are the same, but that means of course that you might see a change. Luckily, you can set the output you want and get the same in both v2 and v3.

\DeclareSIUnit\litre{l}

I’ve just released version 3 of siunitx: its a major update, in which the internals have largely been re-written. The following is a short(ish) summary of the major benefits and changes.

The benefits

The major changes under the hood mean I can get better performance out of version 3 than there was in version 2. For most users, you’ll see something like a two-times speed-up of any use of siunitx. That shows up most if you have complex tables.

The new font control system means that I have to do a lot less to match the running font. So it is a lot easier to ‘do nothing’ than it was with version 2 (where basically you have to undo all of the font changes made by siunitx to get back to where you started!).

There’s new functionality across the board for number processing, and that means I can do more. Most obviously, there is now the ability to round numbers based on their uncertainties. I’ve also removed the oddities and limitations for interaction between parts of the code. Uncertainties can now be formatted using the NIST approach: a long-standing request.

For programmers, there is now a formal documented code-level API and a full set of tests (running using l3build), so it’s a lot easier to be sure what is supposed to happen. You can also re-use bits of siunitx to support other code much more easily than in the past.

Finally, I’ve now got more ability to add new features: I now know how I’m going to deal with multi-part uncertainties, for example. That includes having proper internal structures to make future development easier.

The changes

Now to the things to watch out for: taken from the new manual, and perhaps a bit more formal than the usual blog post!

A significant number of key-value settings have new, more descriptive, names. Where possible, older names are mapped to newer ones internally: you will be warned in the log if this is the case.

It is possible to use the LaTeX kernel mechanism to load the last version 2 release for documents that cannot be successfully processed using version 3. This can be achieved using

\usepackage{siunitx}[=2021-04-09]

or

\usepackage{siunitx}[=v2]

In version 3, the document commands have been revised to be more descriptive. As such, the commands \SI,\SIlist, \SIrange and \si remain available but are not recommended for use in new use.

Some changes have been made to the semantics of commands or options. Most notably

• prefixes cannot now be given without units;
• prefixes can only be interconverted with numbers as part of a quantity, not as stand-alone units.

The font control system has been completely re-written for version 3. The method used is entirely different from version 2. Emulation is therefore not provided for some aspects: if you need non-standard font settings, you will need to adjust your source.

The input approach for version 3 is slightly more structured and restricted than for version 2. As well as the updated names for document commands, this means that

• Products of numbers must now be given using the dedicated \numproduct and \qtyproduct commands;
• Quotients of numbers are only supported as literals;
• Complex values need to be given using the dedicated command \complexnum.

The letter used for a numerical tabular column can now be selected by the user: the letter S has been retained as the standard interface. The unit column (s) has been removed from this release. It can be emulated using the collcell package, for example

\usepackage{collcell}
\newcolumntype{s}{>{\collectcell\unit}c<{\endcollectcell}}

or

\usepackage{collcell}
\newcolumntype{s}{>{\collectcell\si}c<{\endcollectcell}}

A new approach has been taken to providing non-Latin symbols for use in units: these are now handled directly where needed, for example in the definition of the \micro prefix.

If you are using table-column-width to have fixed-width columns, you also now need table-fixed-width to set this option active.

Ursprünglich auf TeX.co veröffentlicht.

Es gibt ja viele Internet-Foren, Blogs, Wikis und andere Webseiten mit Codebeispielen für TeX und LaTeX. Gerade in Foren ist es üblich, Problem-Beispiele zu posten, und Antworten enthalten oft vollständige Lösungs-Codes. Optimalerweise mit Screenshots zum Komfort aller Leser. Man kann sich den Code herauskopieren und in seinem eigenen LaTeX-Editor ausprobieren.

Was, wenn man den Code mit einem einzigen Klick direkt auf der Webseite übersetzen könnte? Am besten auch auf dem Tablet oder Mobiltelefon, wo auch immer man gerade liest?

Das geht nun mit TeXlive.net.

Am besten sieht man es am Beispiel:

\documentclass[border=10pt]{standalone}
\usepackage{smartdiagram}
\usepackage{metalogo}
\begin{document}
\smartdiagram[bubble diagram]{\TeX\ engines,
  \TeX\ (dvi), pdf\TeX, \XeTeX, \LuaTeX, Con\TeX t}
\end{document}

Einfach “Run LaTeX here” klicken. Dann übersetzt LaTeX den Code und er wird hier direkt dargestellt. Durch Klicken auf >> rechts oben kann man die PDF-Datei speichern.

Auch gut zum Testen und ausprobieren: den Code kann man hier direkt auf der Webseite editieren und wieder auf den Ausgabe-erzeugen-Schalter klicken. Das finde ich extrem praktisch in Foren, wo man ein angegebenes Problembeispiel direkt bearbeiten und testen kann, um eine Lösung zu finden und mitzuteilen. Probier einfach aus, indem Du die Diagramm-Texte oben oder das unten folgende Mathematik-Beispiel etwas editierst und erneut übersetzt.

Wie hier zu sehen, erfolgt Angabe der Engine, des Formats, oder des Ausgabeformats durch einen Kommentar

% !TEX name

wobei name z.B. sein kann: latex, pdflatex, xelatex, lualatex, pdftex, luatex, xetex, context, oder für die Ausgabe pdfjs, pdf, log (Logfile), make4ht, LaTeXML or lwarp, und Tools wie makeindex mit Parametern. Siehe auch Beispiele und Dokumentation.

Die Auslastungs-Statistik von TeXlive.net zeigt, dass täglich ungefähr 2000 verschiedene Nutzer ca. 4000 Dokumente übersetzen, an Wochenenden weniger. Das kommt daher, weil TeXlive.net schon in vielen Webseiten genutzt wird und die Nutzer aktiv die Codebeispiele ausprobieren. Hier einige willkürliche Beispiele, die zeigen, dass es auf verschiedensten Web-Plattformen läuft:

• plain TeX auf TeXwelt.de
• Beamer auf TeXnique.fr
• Brief mit LaTeX auf TeXfragen.de (Dokuwiki)
• Titelseite mit KOMA-Script (Mediawiki)
• BibTeX/biber/biblatex auf goLaTeX.de (phpBB)
• tkz-euclide auf LaTeX.org (phpBB)
• pgfplots 3d filling (WordPress)
• Glossaries/makeindex/xindy auf LaTeX.net (WordPress)
• TeXample (Django)

TeXlive.net unterstützt ca. 20 Compiler Engines/Formate einschließlich (pdf)LaTeX, XeLaTeX, LuaLaTeX, plain (pdf)TeX, LuaTeX, XeTeX und ConTeXt sowie Ausgabe via pdfjs, Browser PDF plugin, HTML-Ausgaben mit make4ht, lwarp, oder LaTeXML und Tools wie makeindex, BiBTeX, und biber, kombinierbar.

Warum nicht auch direkt übersetzbaren Code in Twitter-Beiträge einbetten? Das geht mit LaTeX-Dokumenten direkt in einer URL, z.B.: texlive.net/run?\[T_{f(x;a)}=\sum_{n=0}^\infty\frac{f^{(n)}(a)}{n!}\].

Zum Datenschutz: TeXlive.net als Compiler erhält den übergebenen Code, übersetzt ihn und liefert die Ausgabe zurück. Die bei der Übersetzung anfallenden Dateien (PDFs, Logfiles) werden in einer stündlichen Routine gelöscht wenn sie ab 1 Stunde alt sind, d.h. sie liegen 1-2 Stunden vor bis zur automatischen Löschung. Wie bei Webseiten üblich, sieht auch TeXlive.net die IP-Adresse des Aufrufenden (bzw. seines Providers). Webserver-Logdaten (für technische Zwecke (Troublehooting, Performance-Statistik, Schutz gegen Angriffsversuche) werden nach ab 14 Tagen Alter automatisch gelöscht.

Die Software für TeXlive.net wurde von David Carlisle geschrieben, ursprünglich für LearnLaTeX.org, eine multilinguale Tutorial-Seite für LaTeX-Einsteiger, die auch den Online-Compiler in den Lektionen verwendet. Der Server arbeitet mit einem aktuellen TeX Live 2021. Wie die obengenannten Foren und weiteren Webseiten läuft TeXlive.net auf von DANTE e.V. projektfinanzierter Hardware, das sind zwei bei Hetzner laufende Root-Server. Danke an DANTE dafür.

Following up on the recent first beta for siunitx, I’ve now made a second beta available. There was only one issue picked up so far by testers, plus of course those I’ve spotted myself. In particular, I’ve allowed a way to set the text font manually if simply resetting back to the standard one doesn’t work. I’ve also sneaked in a late addition: the ability to parse and print uncertainties the way NIST seem to suggest they should appear.

Assuming that I get no major issues coming up, I plan to put this out as the first v3 release in a couple of weeks time: before the next LaTeX kernel update!

Internal draft for codes.

The third and final LaTeX pre-release for 2021-06-01 is available for testing

A few days ago we submitted a new LaTeX development format to CTAN and by now this should be available to all users using MiKTeX or TeX Live (on any operating system).

Because of the freeze for TeXLive 2021 we have decided to move the release date for LaTeX from May to June, to give everybody enough time for testing the new release features.

Main features of the second pre-release for 2021-06-01

The final pre-release contains all the features, corrections and enhancements that we intend to release in June. The more important ones are listed in the draft publication of LaTeX2e News Issue 33. A full list is given in the changes.txt files that are part of the distribution. Notable improvements are

• better support for copy-and-paste from LaTeX-generated PDF documents by including glyphtounicode mappings;
• support for producing several footnote marks to one footnote with the help of the \footref command;
• additional support for package and class option lists that use key/value syntax;
• extending the general hook management system to paragraphs and commands as discussed below.

Extending the general hook management system to paragraphs and commands

In addition to the bug fixes and enhancements, the next release also extends LaTeX’s general hook management system by supporting paragraph hooks executed at the beginning and end of every paragraph, documented in ltpara-doc.pdf.

This functionality is essential for the production of automatically tagged PDF documents and resolves one of the major obstacles in this area. It is thus an important step in our multi-year journey towards accessible and well-tagged PDF documents. See articles in PDF, Tagging, Accessibility.

Even though this new functionality may not be of direct interest to most users (as long as it is not yet used for processing accessible PDF) it is nevertheless important that it gets tested to ensure that there aren’t any conflicts with existing packages that also try to manipulate the paragraph processing in one way or the other. So please make use of the development format whenever you have a chance, see below for how to do this with ease.

The release will also support generic hooks on all user-level commands; in theory that is, in practice there are some restrictions as explained in the documentation in ltcmdhooks-doc.pdf.

Again this is an important step towards tagged PDF as it will help integrating the necessary code in various user-level commands without extensive code alterations that would otherwise be required. In addition this functionality is also of interest to packages that for one or the other reason currently patch code of other packages or from the kernel as the hook management helps to do this in controlled ways avoiding typical incompatibilities between packages.

Kernel support for the new LaTeX PDF management

We also added the necessary support in the LaTeX kernel and uploaded the new LaTeX PDF management — so far as a separate package for testing. This code is another important step towards well-tagged PDF documents as it provides backend-independent interfaces to central PDF dictionaries, tools to create annotations, form Xobjects, to embed files, and to handle PDF standards. During a test phase this code is provided through an external package named pdfmanagement-testphase. Please help with the testing here too. You can access the documentation through texdoc pdfmanagement-testphase.

Outlook

This is the final prerelease, the same code (modulo any corrections found during testing) is planned as the official June 2021 release.

Please help with the testing

We are issuing this final pre-release now in the hope that you will help us by making sure that all the enhancements and fixes we have provided are safe and that they do not have any undesired side effects, so please help with the testing if you can.

This development format allows you to test the upcoming LaTeX release scheduled for 2021-06-01 with your documents or packages. Such testing is particularly important for package maintainers to verify that changes to the core LaTeX haven’t introduced incompatibilities with existing code. We try to identify any such problems beforehand but such an undertaking is necessarily incomplete, which is why we are asking for user testing.

Besides developers, we also ask ordinary users to try out the new release, because the more people that test the new format, the higher the chances that any hidden problems are identified before the final release in June hits the streets.

Processing your documents with the pre-release is straightforward. All you have to do is to replace the invocation command by appending -dev to the executable, e.g., on the command line you would run

pdflatex-dev myfile    or    lualatex-dev myfile    or    xelatex-dev myfile

instead of using pdflatex, lualatex or xelatex. If you use an integrated editing environment, then it depends on the system how to configure it to use an alternative format; but in any case the necessary modification should be straightforward.

If you encounter any issue with this prerelease, please open a bug report at https://github.com/latex3/latex2e/issues following the guidelines given there (especially providing a processable test document).

In case of incompatibility problems with the prerelease it is, of course, acceptable to report them to us, even if \RequirePackage{latexbug} tells you to report them elsewhere (it would help if you do that too).

Enjoy — Frank

I’ve been talking about a new version of siunitx for ages. Progress has been slow but I’ve now put my back into it and got to a feature-complete version: I’m calling this v3.0.0-beta. As this is a beta release, it’s not ready for production just yet, but it is ready for proper testing. I’ve made the TDS-style zip file available here; if you know how to use this kind of file, please download and test!

As I’ve said before, there are a lot of internal improvements in the code. There are also some big changes which do show to users. The major changes are

• The name for commands for units and quantities have changed: \unit and \qty. The old names (\si and \SI) are still about, but I’d encourage people to move to the new ones.
• Font set up is entirely revised, which means that there are new settings to use if you want to adjust the output. The new approach should be faster and cleaner than the old one, but you might have to pick new options.
• Products of numbers now have a dedicated interface: \numproduct, with a matching \qtyproduct for quantities
• Complex numbers also have decided interfaces: \complexnum and \complexqty: this makes parsing a lot easier
• A small number of ideas have been removed: most notably parsing quotients
• I’ve updated the units provided to match the 9th SI Brochure: that means a few units are removed (for example ängström and bar)

To support users and to avoid breaking any documents, the new code is accompanied by a (likely) final version 2 file. That can be loaded using

\usepackage{siunitx}[=v2]

where needed.

What I’m looking for now is feedback on what works, what I’ve missed, etc. Feedback is best in issues on GitHub. You might notice I’m already planning v3.1 and v3.2: the new structures should make more development possible. But at the moment I’m mainly trying to finalise v3.0.

Hier ein Beispiel dafür, wie man mit dem gridpapers Paket Muster auf Papier bringen kann, hier ein Punktmuster.

%!TEX TS-program = Arara
% arara: pdflatex: {shell: yes}
\documentclass[12pt,ngerman]{scrartcl}
\areaset{8cm}{16cm}
\usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\usepackage{babel}
\pagestyle{empty}
\usepackage[pattern=dot,% 
colorset=std,
geometry={left=2.25cm,right=1.25cm,top=1cm,bottom=1.25cm},%
textarea,%
patternsize={5mm},%
dotsize={1pt}
]{gridpapers}

\begin{document}
~

\end{document}

Auszug aus der A4-Seite:

Uwe

Uwe 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 here Spenden für die Dingfabrik.

More Posts - Website

Hier ein kurzes Beispiel, wie man mit LaTeX auch Dymo-Labels erzeugen kann, im Beispiel für die Label-Größe 57*32mm. Zum allgemeinen Verständnis von ticket.sty siehe auch meinen DTK Artikel in Ausgabe 1/2021.

\documentclass{article}
\usepackage[T1]{fontenc}
\usepackage{graphicx}
\usepackage[landscape,paperheight=57mm,paperwidth=32mm,left=0mm,top=0mm,right=0mm,bottom=0mm]{geometry}
%\usepackage[sfdefault]{plex-sans}
\usepackage{palatino}

\begin{filecontents}[overwrite]{Dymo5732.tdf}
\unitlength=1mm
\hoffset=-25.4mm
\voffset=-29mm
\ticketNumbers{1}{1}
\ticketSize{57}{32} % Breite und Hoehe der Labels in mm
\ticketDistance{0}{0} % Abstand der Labels
\end{filecontents}

\usepackage[Dymo5732]{ticket}
 
\renewcommand{\ticketdefault}{}%
\makeatletter
\@boxedfalse % Rahmen um Ticket
\@emptycrossmarkfalse % Falzmarken
\@cutmarkfalse % Schnittmarken
\makeatother
 
\newcommand{\myticket}[2]{
\ticket{%
\put(10,10){\scalebox{#1}{\bfseries #2}}
}}

\newcommand{\myticketml}[4]{
\ticket{%
\put(5,20){\scalebox{#1}{\bfseries #2}}
\put(5,15){\scalebox{#1}{\bfseries #3}}
\put(5,10){\scalebox{#1}{\bfseries #4}}
}}

 
\begin{document}
\myticketml{1.25}{Dr. Max  Mustermann}{Musterweg 123}{54321~Musterstadt}
\myticket{2}{Steuern}
\end{document}

PDF

Uwe

Uwe 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 here Spenden für die Dingfabrik.

More Posts - Website

Blogs, forums, Q&A sites, FAQ sites, and web sites in general can now provide one-click LaTeX compiling on smartphones, tablets, and PCs.

The TeXlive.net server provides a backend with a TeX Live 2020 installation. The server software was written by David Carlisle and is hosted on a virtual machine provided by Stefan Kottwitz, with financial support from DANTE for the hardware.

The tutorial site LearnLatex.org already switched to TeXlive.net.

That’s how it looks like on a web page:

\documentclass[border=10pt]{standalone}
\usepackage{smartdiagram}
\begin{document}
\smartdiagram[descriptive diagram]{
  {Style,{Define shapes, colors, shading,
          and line styles for nodes and arrows}},
  {Position, {Place nodes using a matrix,
              relative or absolute positioning}},
  {Relation, Insert edges or arrows
             between selected nodes},
  {Label, Add labels on edges or arrows}}
\end{document}

Click on “Run LaTeX here” to open an embedded PDF viewer with the document output. And yes, you can edit the document right on the web page and compile again.

TeXLive.net, LaTeX.net and many further web sites are supported by DANTE e.V., the German language user group. Our 2021 DANTE spring meeting starts today, join us!

The following text is in German because it’s about the German language user group meeting 2021.

Im vergangenen Jahr sind leider beide DANTE-Tagungen wegen der Pandemie ausgefallen.

Dieses Jahr wird die Frühjahrstagung stattfinden, jedoch wegen der Kontaktbeschränkungen komplett online.

Anmelden kann man sich online auf www.dante.de/veranstaltungen/dante2021/anmeldung/ und das ist kurz und einfach und kostenfrei.

Mitglieder erhalten später einen PIN-Code, mit dem man sich an Abstimmungen während der Mitgliederversammlung beteiligen kann. Wie es geht, wird dann in der Versammlung erläutert.

Wichtig: Die Anmeldung sollte bis spätestens Dienstag erfolgen.

Das Programm, vom 9. bis 11. März 2021:

• Dienstag, 9.3.: ab 19:30 Uhr Vorabendtreff
• Mittwoch,10.3.: 17 Uhr Begrüßung, danach 3 Vorträge zu
  • Spaß mit LaTeX für Zuhaus-Unterricht, Videokonferenzen und mehr
  • Lehr-Unterstützung durch automatisiert generierte personalisierte Aufgaben und Lösungen
  • PDF Ressourcen-Management mit LaTeX als Baustein für barrierefreies PDF
• Donnerstag, 11.3.: ab 9 Uhr Mitgliederversammlung, danach Vorträge bis ca. 19 Uhr zu
  • GUST e-foundry Schriftprojekt
  • TikZ-Zeichnungen
  • englischsprachiger TeX Frage/Antwort-Webseite
  • Erstellen von ausfüllbaren PDF-Formularen mit LaTeX
  • Erzeugung von TeX-Ausgaben aus XML
  • Automatisiertem Tabellensatz aus XML und LaTeX

Siehe auch Programm und Tagungs-Seite.

Wie läuft das ab?

Basis ist die Videokonferenz-Software Zoom, lizensiert durch die Universität Magdeburg als Veranstalter. Teilnehmer erhalten einen Zugangs-Link mit Meeting-ID und Kennwort. Darüber kann man sich einloggen und mit einem Webbrowser oder der Zoom-App auf dem PC oder dem Handy teilnehmen. Da hat man zunächst einfach mal das passive Zuschauen und Zuhören der Vorträge, weiterhin kann man aber auch in aktive Räume wechseln zum Unterhalten in kleinerem Kreis. Das sieht man dann schon.

Das Teilnehmen sollte recht einfach sein – kommt dazu! Die Organisation war und ist bestimmt herausfordernd – vielen Dank an Mathias Magdowski, Martin Sievers, weitere Organisatoren und den Vorstand, und an die Vortragenden!

An dieser Stelle auch ein Danke von mir an DANTE für die Unterstützung bei den Serverkosten dieser Webseite LaTeX.net sowie der LaTeX-Foren TeXwelt.de, goLaTeX.de, LaTeX.org, TeXnique.fr, und weiteren Webseiten wie TeXfragen.de, LaTeX.net.br, TeXdoc.org, CTAN.net, TeXlive.net, TeX.my, TeXample.net, pgfplots.net, TeX-talk.net, mychemistry.eu, TeX.co, TeXblog.net und weiteren.

Anmelden.

Photo by Raphael Schaller on Unsplash

The second LaTeX pre-release for 2021-05-01 is available for testing

A few days ago we submitted a new LaTeX development format to CTAN and by now this should be available to all users using MiKTeX or TeX Live (on any operating system).

Main features of the second pre-release for 2021-05-01

The first pre-release was just a copy of the main release for 2020-10-01 in order to avoid that people using the development release regularly get an old format.

The second pre-release now provides a number of smaller enhancements and resolves roughly forty issues. The more important ones are listed in the draft publication of LaTeX2e News Issue 33. A full list is given in the changes.txt files that are part of the distribution. Notable improvements are

• better support for copy-and-paste from LaTeX-generated PDF documents by including glyphtounicode mappings;
• support for producing several footnote marks to one footnote with the help of the \footref command;
• additional support for package and class option lists that use key/value syntax;
• extending the general hook management system to paragraphs as discussed below.

Extending the general hook management system to paragraphs

In addition to the bug fixes and enhancements, this second pre-release also extends LaTeX’s general hook management system by supporting paragraph hooks executed at the beginning and end of every paragraph.

This functionality is essential for the production of automatically tagged PDF documents and resolves one of the major obstacles in this area. It is thus an important step in our multi-year journey towards accessible and well-tagged PDF documents. See articles in PDF, Tagging, Accessibility.

Even though this new functionality may not be of direct interest to most users (as long as it is not yet used for processing accessible PDF) it is nevertheless important that it gets tested to ensure that there aren’t any conflicts with existing packages that also try to manipulate the paragraph processing in one way or the other. So please make use of the development format whenever you have a chance, see below for how to do this with ease.

Kernel support for the new LaTeX PDF management

We also added the necessary support in the LaTeX kernel and uploaded the new LaTeX PDF management — so far as a separate package for testing. This code is another important step towards well-tagged PDF documents as it provides backend-independent interfaces to central PDF dictionaries, tools to create annotations, form Xobjects, to embed files, and to handle PDF standards. During a test phase this code is provided through an external package named pdfmanagement-testphase. Please help with the testing here too. You can access the documentation through texdoc pdfmanagement-testphase.

Outlook

We expect to produce a third and probably final pre-release adding some more features and enhancements in early April.

Please help with the testing

We are issuing this second pre-release now in the hope that you will help us by making sure that all the enhancements and fixes we have provided are safe and that they do not have any undesired side effects, so please help with the testing if you can.

This development format allows you to test the upcoming LaTeX release scheduled for 2021-05-01 with your documents or packages. Such testing is particularly important for package maintainers to verify that changes to the core LaTeX haven’t introduced incompatibilities with existing code. We try to identify any such problems beforehand but such an undertaking is necessarily incomplete, which is why we are asking for user testing.

Besides developers, we also ask ordinary users to try out the new release, because the more people that test the new format, the higher the chances that any hidden problems are identified before the final release in May hits the streets.

Processing your documents with the pre-release is straightforward. All you have to do is to replace the invocation command by appending -dev to the executable, e.g., on the command line you would run

pdflatex-dev myfile    or    lualatex-dev myfile    or    xelatex-dev myfile

instead of using pdflatex, lualatex or xelatex. If you use an integrated editing environment, then it depends on the system how to configure it to use an alternative format; but in any case the necessary modification should be straightforward.

Enjoy — Frank

Unter https://gist.github.com/iwishiwasaneagle/2f91f63f3cb0107b94b501aa284a18ca gibt es eine Sammlung an nützlichen Einzeilern für die Arbeit mit LaTeX.

Uwe

Uwe 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 here Spenden für die Dingfabrik.

More Posts - Website