Closed lstngr closed 1 year ago
In his answer
in her answer. I'm a women.
I was wondering if this was a bug, or expected behavior
I will have to check but probably more expected behaviour then bug. In any case you shouldn't rely on internal expansion, but expand yourself by using the "x" argument type:
\pdfmanagement_add:nnx{Pages}{TrimBox}{[\l_soli_trimbox_tl]}
\pdfmanagement_add:nnx{Page}{TrimBox}{[\l_soli_trimbox_tl]}
In a current LaTeX you can/should also replace
\RequirePackage{pdfmanagement-testphase}
\DeclareDocumentMetadata{uncompress}
by
\DocumentMetadata{uncompress}
in her answer. I'm a women.
Sorry, I should have checked.
Thank you for the prompt and useful help, it indeed looks like a misunderstanding of expl3 on my side, sorry for the "pollution" this issue caused!
I've been trying to set the TrimBox of my document based on layout computed by the geometry package. The idea being to implement something along the lines of Ulrike Fischer's answer on the TeX StackExchange. In her* answer, the computed TrimBox values are stored in a token list and written to the PDF page attributes.
I've tried replicating this answer using the pdfmanagement-testphase package, but noticed that the MWE below behaves differently when compiling with pdflatex or lualatex. With pdflatex,
\t_soli_trimbox
is correctly expanded when passed topdfmanagement_add
. However, lualatex seems to "sometimes" expand it.With pdflatex
With lualatex,
I was wondering if this was a bug, or expected behavior, since the pdfmanagement-testphase mentions backend dependent behavior in some cases. Being unfamiliar with the expl3 syntax, pardon me if this was expected (and I'd be glad if you'd let me know what could have been done better!).
Edit: below are the versions of pdflatex and lualatex that were used.