@JosephWright the pdf77... is a trivial change (only makes an unknown standard an error) and can be merged. The float one is WIP. It will be ready today. But Frank should perhaps see it as it changes multicol
Wy does this error if placed in the preamble of a doc. Fonts not set up? \ExplSyntaxOn \coffin_new:N \l_A_coffin \vcoffin_set:Nnn \l_A_coffin { 4cm } { Ag \\ Ag \\ Ag } \ExplSyntaxOff Works fine if placed after `\begin{document}`.
@daleif fonts are not set up fully but the error is (as has always been the case in latex) you can not set paragraph text before begin document. hmode hbox can be typeset/measured in some cases, but \everypar has always given the missing begin document error.
If using coffins instead of \parbox, what extra things are needed to be manually added for it to behave like \parbox, I've notived fx that the text is indented. \@parboxrestore? Pole feature was something I could use in a project, where I have text in two boxes. The text should align on the top baseline, and the lowest baseline in the entire thing should then be placed on the overall baseline.
@DavidCarlisle That expain it. In my Expl conversion project, I've been using hbox_set with parboxes inside. Should probably use low level coffins instead.
A bit sad that the poles syntax is not independently explained in interface3 as xcoffins is marked experimental. So without looking in the xcoffins manual one cannot use the stuff from l3coffins as the pole notation is never explained.
@JosephWright So the l3coffins stoff might change in the future? It is more, can I use it or not. Again, the end product here will not be public, so updating is a little funky.
@daleif I think we may need some refinement still, but we are committed to the code in general, so it would have to be to address serious issues - most cases would clearly have to be unchanged
Erh, is playing with l3doc, and has \@@par in some code (do not remember why). But the tex on the ins file converts \@@par to \__module-xpar, how do I make it stop? The code is just inside a normal macrocode.
@DavidCarlisle Ahh, that us what what thing is doing (I had stolen some code from siunitx.dtx). I just removed the <@@=module> line, I was wondering where a random - and x came from, I had <@@=module-x>.
Are other packages still messing with the class options? I'm using l3keys to setup class options as key=val, and I seem to still get Unused global option(s) for all the key=val options that were used.
@daleif Might happen, yes. There was a breaking change in the tracking of unused class options that many key=value packages haven't yet caught up to (and some never will)
@daleif OK, although using foobar for the class options (to match what \ProcesskeyOptions expects, and will be seen in most other classes using this) is still possible even if you use foobar/something for more specific keys elsewhere
@DavidCarlisle ?? overleaf also times out. but I'm inclined to abandon my attempt to create an mwe. it just crashes konsole. only I'd feel happier if I could figure out why in case the actual file can do the same thing. (it doesn't but I've no idea what the difference is.)
@cfr well yes but then you need to ask him not ctan:-) basically only other requrements for texlive are open-source things like having source of any pdf doc
