We are now looking at using it 'in anger' for lists, etc., as part of the tagging project: there are some adjustments to make, mainly to allow 'dynamic' keys to be applied. Things like supporting `enumitem`-like setups.
... somebody (or someduck) mentioned it in a chatroom the other day :) I wasn't aware of this package before, but I like the concept!
I'm currently working on `xtemplate`: we are likely to (finally) pick up some of these ideas and move to the kernel soon-ish
I suggest to replace “It’s other original strength” with “Its other original strength” on page 1. :-) (I suppose you can update the source...)
Yes, TL2022 is needed. The commit is from the start of the year https://github.com/josephwright/beamer/commit/3659a643cd3ac179bf526db33269e6a9102d1768
I also added a nswer answer: https://tex.stackexchange.com/questions/14336
BTW, I just tested the option in the newest Overfaf version and it does not seem to work:  Maybe it was introduced after TexLive 2021.
understandable (I created a wrapper class around `beamer` once, and that one added the colon-syntax)
Short version: if in doubt, it assumes landscape format (a bit) longer version: 
Sure! There is no need to reference this conversation, the mechanism is not secret, it is documented in the user guide
How does the code know if it should combine the first two or the last two digits if the user only provides 3 digits? Meaning `161` could mean `1:61` or `16:1` or `16:10`. I assume it always fills up zeros to have 4 digits and then takes 2 and 2.
Could I provide a new answer on https://tex.stackexchange.com by referencing this chat?
I thought about this for quite some time when making these changes, but I didn't like the idea of having two different syntax floating around ....
Indeed! And even across the previously defined ratios, the format isn't consistent. The fact that it is `141` and not `1410` (like `1610`), really drives me crazy :)
(also, patching that in with backwards compatibility doesn't seem too hard, check whether an old one, check whether without a colon, use the sane syntax)...
I miss a separator in the aspect ratios of `beamer` (imho, it should be `aspectratio=16:9` or the like)
(I got a bit tired of all the feature requests about new aspect ratios, some of which resulted in geometries with less than 1% difference to existing ratios, so I thought to just let the users have their fun :) )
@Dr. Manuel Kuehner I saw your edit on the aspect ratio answer. It is a bit outdated thought, because beamer now also supports undefined ratios and calculates the necessary dimensions on the fly, e.g. one can do ``` \documentclass[aspectratio=161]{beamer} \begin{document} \begin{frame} content... \end{frame} \end{document} ```
I really like the simpleicons package - makes documents look way cooler with little effort.
Thanks for the answer and sorry for my late reply...life got in the way :).
Thanks for the answer and sorry for my late reply...life got in the way :).
Thanks for searching! I'm using vanilla texlive on mac os. Henri found a link to the kpathsea sources, so I'll try to build them now. If this does not work I'll try with libkpathsea on a linux box tomorrow.
The Debian package `libkpathsea-dev` ships `/usr/include/kpathsea/kpathsea.h`, however building against it is not correct in principle if you are using TeX Live from upstream... As the [`dvisvgm` README](https://raw.githubusercontent.com/mgieseki/dvisvgm/master/README) says: > This library is part of the Web2C package and is usually installed in conjunction with a TeX distribution. `kpathsea` provides functions for searching files in the large texmf tree. Please ensure that you use the `kpathsea` version coming with or matching your TeX system.
I tried building it from source, but I am missing `kpathsea.h`. Does anybody know if this is supposed to be included in texlive or do I have to install it separately?
Oh, sorry, it's a binary. That slipped my brain for a moment. As Norbert said, binary updates are only(ish) done at the beginning of a new TL version. Depending on what you need the fixed version for, you could build the binary yourself and replace the TL one.
(now asked in the matrix texlive chat https://matrix.to/#/!lMtRnfTLBEMGxhtokD:matrix.org/$2oDce7JEAQVDJaTkCw1li_vROLcB049XlvbbtnLIPAM?via=matrix.org&via=im.f3l.de&via=2krueger.de )
@Phelype @frougon Thank you both! I just wanted to check if it is only me or if others can reproduce before asking on TL
I just ran `tlmgr update --all` and also have dvisvgm 2.13.3 according to `dvisvgm --version`.
Hm... By the time stamp, it should be there already. You might want to ask on the TL list
I'm eagerly waiting for a new dvisvgm version which seems to be on ctan since two days (https://www.ctan.org/pkg/dvisvgm), but I did not yet get an update via texlive. `dvisvgm --version` still says 2.13.3. Can anyone reproduce or might this be a problem at my end?
I think there are way too many people like that already, so the impact by those additional questions is barely noticable.