Open chrislandis opened 1 year ago
I think the usage of \lTblrMeasuringBool
should be added to the code of acro
package, so that normal users need not to worry about this problem.
I think the usage of
\lTblrMeasuringBool
should be added to the code ofacro
package, so that normal users need not to worry about this problem.
I agree that the ideal configuration involves all acronym packages incorporating the use of \lTblrMeasuringBool
so that users do not need to worry about it. However, I offer the following reasons why we should still document it in the tabularray
documentation instead of just leaving users to find it in the tabularray
source code:
Acronym packages, including acro
, acronym
, and others, have relatively little incentive to install hooks to tabularray
to support this edge case of using the tabularray
package with first-appearance acronyms in the tables.
Although tabularray
is superior to other table packages in many (all?) ways, my observation is that most LaTeX users have not yet transitioned from those other table packages to tabularray
so there is less demand/incentive for these acronym package owners to incorporate it.
Depending on someone else's voluntary work on their packages to improve tabularray
's usage with those packages may not yield the intended outcome of improving users' experience with tabularray
because they might not ever get around to it.
Describing the use of \lTblrMeasuringBool
in the tabularray
documentation empowers (makes it easier for) various acronym packages to incorporate its use into their packages and gives users a reference to link to when contributing this to these other packages/projects. In other words, documenting the capability here first will help with others incorporate it in their packages.
Describing the use of \lTblrMeasuringBool
in the tabularray
documentation empowers users to innovate more with the tabularray
package, thus encouraging more users to adopt or transition to it.
This updates the
tabularray
documentation to reflect the changes made to support issues #179 and #399.