lvjr
lvjr
@mateusfccp You may have a look at the following answer of mine: https://tex.stackexchange.com/questions/645421/tabularray-with-footnotes/645453#645453
I needs to clean up them step by step and case by case. Maybe I can start from variables used in tikz library.
Or make `tabularray` behave like `longtable`: it needs multiple compilations to get the final result, but only measures once in each compilation.
Issue #100 (about X columns with both `co` and `wd` settings) is related.
@note286 You can use `X` columns with negative coefficients. The result is similar (but not totally the same) to that of manually setting `colsep=7.5pt`. See the documentaion of `tabu` package...
I am planning to add a new inner key `hspacing` which takes the following possible values: - `default`: distribute total available space to the widths of `X` columns. - `fixed`:...
>When all column formats are negative, how is the width of each column allocated? Columns with larger natural widths get more extra space. You could read chapter 11 of `tabu`...
>A positive number means that the column width is fixed Sorry, it turns out that my memory on `X` columns is inaccurate: when *all* coefficents of `X` columns are positive,...
We can also consider what `tabulary` package does: distributing widths according to natural widths of columns. See discussion https://github.com/lvjr/tabularray/discussions/397.
There is one problem if we want to follow what `tabular*` does: if the natural width of a table is larger than `\textwidth`, the table will overflow. Should we do...