Replies: 3 comments 1 reply
It is the cost of quality, because TeX doesn't provide a native data stucture for reading and writing key-value pairs. (Also
Possible, but not that easy.
There is some tracing information in the log by default: And you can print more with
I think LuaTeX is the only possible way to go. PS: please test version 2022C. I believe it is faster than 2022B but not sure how much. |
|
There is a tip for faster rendering: fixing all column sizes. |
|
I have created a new related issue: https://github.com/lvjr/tabularray/issues/274 . |
Uh oh!
There was an error while loading. Please reload this page.
We use tabularray with the "long" option a lot, for its superior output quality. However, the rendering is quite slow (>10 seconds for a two-pages document, with longtable it's <1 second).
I wonder if this package could support a "draft" mode that would perhaps omit some of the expensive computations, perhaps at the expense of output quality?
Could there be a "verbose" or "logging" mode that would print detailed information on what tabularray is doing, perhaps with a time stamp?
I saw #250, but this seems a lot of effort, and I'm not sure we can switch to LuaLaTeX today.
All reactions