lvjr
lvjr
Yes, this is just a minor step.
It seems we can also compile the benchmark file with programs in `latex-dev`.
I did some tests by compiling `tblrbenchmark.tex` four times with different engines in Windows, and from the results of used time it seems current `tabularray` is much faster than previous...
From now on every benchmark result will be published to the following urls in gh-pages: + for texlive 2023: https://lvjr.github.io/tabularray/benchmark/2023 + for texlive 2024: https://lvjr.github.io/tabularray/benchmark/2024 The `benchmark.lua` script compares running...
Benchmark page for texlive 2022 was also added: https://lvjr.github.io/tabularray/benchmark/2022 .
> > ... it seems current `tabularray` is much faster than previous `tabularray` (v2024A). Why? I can not find the reason from the commit log. 😕 > > [`git bisect`](https://git-scm.com/docs/git-bisect)...
This deserves to be mentioned in "Tips and Tricks" chapter.
The LaTeX format doesn't provide a public interface for clearing existing floats without creating a new page. Therefore `tabularray` can do nothing for this problem.
Now that we have tikz library (issue #29), it is better to draw these lines with tikz.
I think this is a feature request for `tex4ht` project. And I guess this is the correct place: https://puszcza.gnu.org.ua/bugs/?group=tex4ht