Good to know that the biggest syntax strangeness of `pgfkeys` that is the `.try`-handler doesn't help in what should be its use case :P
(and before you run into the same problem, the `.try` handler won't work -- something about how the `actualtext` option is defined. Ulrike had some nice explanation, but I can't find it right now...
That's why I'm testing with
```
\pgfkeysifdefined{/tikz/actualtext/.@cmd}{
}{
\pgfkeys{/pgf/actualtext/.code={}}
}
```
)Basically something like this:
```
\DocumentMetadata{tagging=on}
\documentclass{article}
\RequirePackage{tikz}
\makeatletter
\pgfkeysifdefined{/tikz/actualtext/.@cmd}{
}{
\pgfkeys{/pgf/actualtext/.code={}}
}
\makeatother
\begin{document}
text
\begin{tikzpicture}[actualtext={42}]%
\draw (0,0) -- (1,1);
\end{tikzpicture}
\end{document}
```Yes, I'm using the `actualtext` tikz option to provide the number as alt text.
Did you already add tagging support to `cistercian`? If so, I might have to copy bits of it, I still haven't reworked my bunch of packages for tagging.
That concludes the package war between `xistercian` and `cistercian`, to the victor go the spoils!
Indeed! Even in colour! That was a really great surprise when reading the Komödie!
@samcarter finally got to take a look at the 4/2025 DTK, `cistercian` got an entire advertisement page!
https://www.newscientist.com/article/2502335-what-the-evolution-of-tickling-tells-us-about-being-human/ ^^^ at first glance, I read the headline as "What the evolution of *tikzling* tells us about being human" :)
Hi all. This is not exactly TeX, but fits equally well in the *BDSM Computer Programming* section: [Ray Tracing in pure CMake](https://64.github.io/cmake-raytracer/). With multicore support. 616 lines of—as much as CMake allows—readable code. Respect. Note: PNG support not required; you can just use the CMakeLists.txt after commenting out its `include(png.cmake)` line.
That's good! Otherwise it would be real torture to leave you waiting until xmas :)
Oh, I've just seen your commit. It seems we were adding it at the same time :)
done (the folder can't be empty, so I added a placeholder image -- just ignore :) )
Three times `freemath` under the incoming packages. Do they want to become the new easybook?
Ahhh, even more broke, the tail handling is in ruins as well (and the new variant will be much more complicated ;()
Friends I found a bug in `ducksay`. Without me noticing (there are no unit tests for it in place) `\AddColoredAnimal` broke sometime since TL2024-frozen to today (there were changes in the kernel on handling spaces/tabs in verbatimly grabbed arguments that caused this which changed the argument from being entirely stringified to having natural catcodes except for `\dospecials` -- and I used a rather restrictive regex that only detected catcode 12 tokens for `\AddColoredAnimal`). As a result I can release a new version of the package. With all that history-lesson out of the way: Which animal shall be added?