From #CTAN:
Oliver Beery submitted an update to the scaletextbullet package.
Version: 2.0.3 2025-10-14
License: lppl1.3c
Summary description: Resize the \textbullet without changing its vertical center
#TexLaTeX
From #CTAN:
Alceu Frigeri submitted an update to the xpeekahead package.
Version: 1.2 2025-10-14
License: lppl1.3c gpl
Summary description: A simple way for peeking ahead after commands and environments
From #CTAN:
Matthias Fresacher submitted an update to the pmdraw package.
Version: 2.1 2025-10-14
License: lppl1.3
Summary description: Draw elements of the diagram monoids
From #CTAN:
Boris Veytsman submitted an update to the arsenal package.
Version: 1.0 2025-10-13
License: ofl lppl1.3c
Summary description: Open Type font by Andrij Shevchenko
From #CTAN:
Jasper Habicht submitted an update to the rpgicons package.
Version: 2.0.3 2025-10-13
License: lppl1.3c
Summary description: Icons for tabletop role-playing games
From #CTAN:
Sigitas Tolušis submitted an update to the sttools package.
Version: 3.4 2025-10-13
License: lppl1.3
Summary description: Various macros
From #CTAN:
Sadao Massago submitted an update to the latex-via-exemplos package.
Version number: 2025-10-12
License type: lppl1.3c
Summary description: A LaTeX course written in Brazilian Portuguese language
https://mirrors.ctan.org/info/latex-via-exemplos
#TeXLaTeX 🇧🇷
@khzimmer2 Das, was ich da im Augenblick mache, dient in erster Linie mir. Zum einen mache ich mich weiter mit #TeXLaTeX Templates (→ lttemplates-doc.pdf) vertraut – oder eigentlich, wie man deren Beschränkungen umgehen kann. Das wiederum will ich nutzen, um die Interna von tocbasic aufzuräumen, die zu einem Zeitpunkt entstanden sind, als ich bei der produktiven Verwendung von #TeXLaTeX3 für #KOMAScript noch Vorbehalte hatte. Ob das am Ende gelingt, steht noch auf einem anderen Blatt.
From #CTAN:
Cédric Pierquet submitted the tkz-interval package.
Version: 0.1a 2025-10-12
License: lppl1.3c
Summary description: Interval brackets made with TikZ
From #CTAN:
Rajeesh KV submitted an update to the ArsenalMath package.
Version: 0.9.1 2025-10-11
License: ofl
Summary description: Arsenal Math OpenType fonts
From #CTAN:
em Övet submitted the beamertheme-bilkent-econ package.
Version number: 0.1 2025-09-21
License type: lppl1.3c
Summary description: LaTeX Beamer theme for the Department of Economics at Bilkent University
From #CTAN:
The LaTeX Project Team submitted an update to the latex-tagging-status package.
Version: 2025-10-12
License: lppl1.3c
Summary description: The LaTeX Tagging Status data
From #CTAN:
KKTeX submitted an update to the KKsymbols package.
Version number: 1.0.3 2025-10-12
License type: lppl1.3c
Summary description: LaTeX commands for enclosing characters in circles, squares, diamonds, or brackets
Heute wieder den ganzen Tag am l3-Interface für ToC-Einträge für das #TeXLaTeX-Paket tocbasic gearbeitet: designen - coden - testen - coden - testen - … Heute Abend dann einen Design-Fehler entdeckt: entsetzen - beruhigen - Design überdenken - Idee für notwendige Korrektur zur Rettung der Grundidee notieren - Updates installieren - E-Mails lesen - Feierabend machen. Wahrscheinlich wäre ich schon weiter, wenn ich nicht versuchen würde LaTeX-Templates für meine Zwecke zurecht zu biegen.
Da aktuell bei #TeXLaTeX die nächste Release ansteht und im Zuge dessen latex-dev gerade finalisiert wurde, ist jetzt übrigens ein idealer Zeitpunkt dafür, das testweise für _alle_ Dokumente zu nutzen. In den meisten Editoren kann man dazu einfach in den Einstellungen das Programm pdflatex bzw. pdflatex.exe durch pdflatex-dev bzw. pdflatex-dev.exe (entsprechend für luatex) ersetzen.
Ich wurde vor einigen Tagen mal wieder gefragt, wie man als reiner #TeXLaTeX-Anwender die #KOMAScript-Entwicklung unterstützen und mich entlasten kann. Eine ganz einfache Möglichkeit ist, häufiger Dokumente mit pdflatex-dev bzw. lualatex-dev statt pdflatex bzw. lualatex zu erzeugen. Je früher Inkompatibilitäten entdeckt und vorzugsweise dem LaTeX-Team gemeldet werden, desto unwahrscheinlicher ist, dass ich mich in einer Hauruck-Aktion nach der nächsten LaTeX-Release befassen muss.
A talented font artist from India Rajeesh KV added math to the beautiful typeface Arsenal by a Ukrainian artist Andrij Shevchenko: https://ctan.org/pkg/arsenal-math
A rare example of a sans serif font with the full math support.
@Harald
LaTeX is really a special purpose programming language for setting text - you run a program to get the final output. While it runs, things expand to other things under the hood, so defining things that expand to other things yourself is not really any different to what it's doing all the time.
(It has a lot of general purpose programming language features such as conditionals, too)
Whereas HTML has no programming facilities and is simply a markup language. It kind of is the final output — of course interpreted by a browser, but any file format has to be interpreted by a program to view.
CSS does have features that creep towards being a programming language, but it's really there to present the content in the HTML, not to change the content in the HTML. Some browsers don't do much of anything with CSS (e.g. lynx or emacs's eww), and I wonder what screen readers would make of this.
(@ArneBab says there are accessibility concerns, I note)
Having HTML that requires no further processing apart from an HTML client to get at that content (not even CSS) is more robust and a better long term solution. There's no software to fail or to not have available apart from a browser, which are readily available, and in some future or some platform where they are not available a simple browser is relatively easy to implement, or someone could just read the HTML directly.
If you want expansion, it would be better for the above reasons to use a program to expand any such abbreviations before publishing.
Fortunately emacs is such a program so I second the recommendations to look into abbrev, hippie-expand, or yasnippit (which is more than you need for this but has other capabilities).
Alternatively you could filter it through an external program to perform what amounts to macro expansion (a step akin to running the latex program over your latex source).
There are many things that could do this, including sed or even the C preprocessor. You could even write your own.
The classic solution would be m4.
(once upon a time I used this to produce slightly different versions of a site for local testing and production, which had different root directories and so forth.)
I imagine it's not worth it to you to introduce such a step, but you may as well know what your options are.
#emacs #html #texlatex #m4
LaTeX is really a special purpose programming language for setting text - you run a program to get the final output. While it runs, things expand to other things under the hood, so defining things that expand to other things yourself is not really any different to what it's doing all the time.
(It has a lot of general purpose programming language features such as conditionals, too)
Whereas HTML has no programming facilities and is simply a markup language. It kind of is the final output — of course interpreted by a browser, but any file format has to be interpreted by a program to view.
CSS does have features that creep towards being a programming language, but it's really there to present the content in the HTML, not to change the content in the HTML. Some browsers don't do much of anything with CSS (e.g. lynx or emacs's eww), and I wonder what screen readers would make of this.
(@ArneBab says there are accessibility concerns, I note)
Having HTML that requires no further processing apart from an HTML client to get at that content (not even CSS) is more robust and a better long term solution. There's no software to fail or to not have available apart from a browser, which are readily available, and in some future or some platform where they are not available a simple browser is relatively easy to implement, or someone could just read the HTML directly.
If you want expansion, it would be better for the above reasons to use a program to expand any such abbreviations before publishing.
Fortunately emacs is such a program so I second the recommendations to look into abbrev, hippie-expand, or yasnippit (which is more than you need for this but has other capabilities).
Alternatively you could filter it through an external program to perform what amounts to macro expansion (a step akin to running the latex program over your latex source).
There are many things that could do this, including sed or even the C preprocessor. You could even write your own.
The classic solution would be m4.
(once upon a time I used this to produce slightly different versions of a site for local testing and production, which had different root directories and so forth.)
I imagine it's not worth it to you to introduce such a step, but you may as well know what your options are.
#emacs #html #texlatex #m4
Client Info
Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst