oh, just revisited the stuff I was sure was added by `xcolor` and not part of `colortbl`, only to find out that it got merged into `colortbl` at some time, so now it really just loads `colortbl` with the `table` option.
actually there are some things that `\usepackage[table]{xcolor}` adds that aren't part of `colortbl`.
No, for real. I thought penguins stuck together for life (heard it somewhen somewhere). Another piece of information I held for granted shattered.
Seen in an old post today: ``` \usepackage{colortbl} \PassOptionsToPackage{table}{xcolor} \usepackage[table]{xcolor} ``` I guess somebody wanted to be extra sure that `colortblr` is loaded :P
The https://ctan.org/pkg/tikzpingus package could do the artwork for the show :P
wait, wait, wait. There are divorced penguins? I thought those stick together for life?!
Great! I'll keep you in the loop! (and would be great to see you there!)
yes, sounds excellent (after all, you do all the work up front :) Just write/ask if you need any help)
I think they should make a reality television series about the penguins. I would certainly enjoy it :)
How about the following plan: I'll submit an abstract for one talk about both packages and closer to Dante'26, we communicate again if you want to do the part about xistercian yourself, otherwise I'll do the whole talk. Does this sound acceptable?
Anyway, lovely idea. I'm always reluctant to give talks about my own packages (well, and for that reason never done so). I like them. I use them (from time to time). But I'm wary whether they're relevant to a broader audience (even though I solve peoples' problems online using them, as there's often another way without using any of my packages).
I think it would be kind of boring to get two talks about Cistercian numerals. But I'm open to collaborate. I don't know for sure yet whether I'll attend (the location is close-ish so that's a plus, but as I said, I'm not sure yet)
@Skillmon The latest Komödie opened the call for presentations at Dante'26. So I'm pondering about doing a short presentation about the cistercian package. I think it might be nice to include xistercian as well, what do you think? Maybe first an intro what these numerals are, then some examples with both packages? Or might you be at Dante'26 and could be persuaded to talk about xistercian yourself?
Perhaps latex isn't the right tool for this task? Saw a few places suggesting scribus with scripting.
On another note, does anyone know of a way to build photo albums with latex? Ideally without actually writing down the whole latex, but with just adding the data files like images and their captions. photoalbum looks like a nice way. https://github.com/flynx/photobook/ But I have trouble understanding the expected directory structuring in their example. https://github.com/flynx/photobook/tree/main/examples/book
https://github.com/settinger/selectric_typeballs ... why do I suddenly think the world needs a typewriter with ducks?
Er, yeah ... we thought about active-`$` but it didn't seem like a plan
It could go like this (typing the numbers from memory, I hope I don't screw up): `\` remains 0, `{}` remains 1 and 2, `%` remains 14, `[A-Za-z]` remain 11, everything else is active.
Sure, but I still hope that one day we might manage to sort out some 'fixed active list' in the kernel ..
Well, except when you don't provide any options, in that case, `expkv` is actually faster than `keyval`. So I can say that `expkv` *is* the fastest
it's "yet another key system", and it's one of the greatest of them for its peculiar syntax.
But yes, `keyval` is the fastest among them all: 
Also, `babel` shorthands are the reason I can claim that only 4 of the key=value parsers I tested work reliably (of which `expkv` is by far the fastest)
**Blog post:** A biased study with one individual finds that a user, who does not use babel shorthands, does not experience a lot of advantages from them, but sometimes finds funny problems they cause. :)
I'm considering starting a tally sheet with "Number of problems solved by babel shorthands" vs. "Number of problems caused by babel shorthands" :)
another implementation for form fields is in the pdfmanagement-testphase package, see all the files starting with `l3pdffield` here https://github.com/latex3/pdfresources