Und nachdem nach der #BayTeX2024 ja vor der nächsten BayTeX ist… wir haben schon etwas überlegt … Aber falls ihr zufällig in Bayern lebt und gerne man eine Mini #TeX / #TeXLaTeX Konferenz organisieren und damit eine leichte Anreise haben wolltet …

Ich glaube es gibt noch keinen Ort für nächstes Jahr.

Und wenn es sich terminlich einrichten lässt und wir dürfen, kommen der Löwe und ich auch, wenn wir nicht mehr in Bayern sind gerne vorbei. Können auch Franzbrötchen mitbringen ;-)

Nach der Mittagspause hat @leah etwas technische Font-Geschichte vorgestellt. Das Tool pkfix kann benutzt werden um in #PostScript-Dateien, die mit dvips generiert wurden die #Type3Font Bitmap Schriften durch #Type1Font zu ersetzen.

Damit kann man alte pixelige Dateien einfach etwas schöner machen indem die Schrift ersetzt wird. Noch schöner ist allerdings die Quelldateien aufzuheben ;-)

Da wir gerade beim Thema sind: Kennt jemand sowas für #PDF?

@heiseonline
Weiß jemand, was.das für ältere #TeX-Documente bzw. deren #PDF-„Drucke“ bedeutet? (#TeXLaTeX #Type1)

#TUG2024 day 3 starts with the status update by Ondřej Sojka about his work on expanding the #hyphenation patterns across Slavic languages.

They use #MachineLearning to compare existing patterns to find out if they can be used or adapted to other Slavic languages.This work is not only to be used within #TeX / #TeXLaTeX of course and is (or will be) implemented e.g. in browsers or smartphone operating systems.

Preprint: https://tug.org/tug2024/preprints/sojka-slavic.pdf

[2/2] Same with the tagging sockets.

So just in case you are or plan to develop a package have a look at the publications of the #TeXLaTeX Project to keep yourself up to date with the common interfaces. It's much more helpful if people actually use those instead of having a huge bunch of packages implementing their own auxiliary macros as it was necessary back in the 90s.

You find them via https://www.latex-project.org/ or locally running `texdoc ltnews`

[1/2] Spreading new concepts or improvements within the #TeX world is always a bit hard. Sadly there's a lot of users (or publishers) who sadly prefer to keep everything the way it was before. The more important it is that active developers use those interfaces instead of creating their own, as we now know, it's hard to clean that up in case there are incompatible changes.

Frank Mittelbach from the #TeXLaTeX project is once again talking about hooks to make developers using them. #TUG2024

@norbu presenting #OpenAccess trying to include that aspect at #arxiv.

I've been following the amazing work by @dginev towards #ar5iv for quite a while and in case you might have missed that:
https://ar5iv.labs.arxiv.org/

There's still a lot of work left, but I really love to see progress towards accessibility within the #TeX / #TeXLaTeX and generally #ScientificPublishing community. Especially showing arXiv it's possible to improve on a huge scale.

Last talk of the session is Joseph Wright speaking about the concept of templates in the #TeXLaTeX kernel.

The concept of providing common interfaces for Layout adjustments exists for a long time within the #TeX world but is now a thing which is pushed by the current development status, as it simplifies preserving the tagging while allowing more flexibility for the layout.

This is using the joy of #expl3 to some higher level commands towards the users.

https://ctan.org/pkg/xtemplate

#TeX / #TeXLaTeX infrastructure has grown wild in huge parts. Trials to modernize are in progress. One step recently taken is presented by Didier Verna talking about the TFM (TeX Font Metrics) validator.

The daily results for #TeXLive are published via https://texlive.info/tfm-validate/fonts.html

And it's not surprising to see that as soon as there are tests one finds issues in published projects. Totally matches my findings. We need more automated testing!

And I know it's a lot of work…

The “rewite it in #Rust” movement reached the #TUG2024 and therefore the #TeX / #TeXLaTeX world. Tyge Tiessen talking about his trial and how wrong he was thinking about it as “a small side project”.

Sadly he started with TeX82 which means it had a bunch of limits we nowerdays don't have anymore. It doesn't provide pdf output and some other limits but in case you were thinking about a rewrite, you might be interested in his work: https://github.com/tyti/rtex

Martin Ruckert is explaining how and why one would like to do profiling for #TeX/#TeXLaTeX and friends. Showing small examples of how to optimize macros and also giving a realistic idea of how much it would change.

Time is one thing, but beside this he also points to the CO2 footprint.

Now I am wondering, if we should use this to compare TeX & Friends to word processors or DTP software. But one would also have to take the editor in account…