With Cleveref, how can I reference a definition in a cited work?
I was tempted to write "we refer to Def.~3.4 in~\cite{...}", but then realized that I want "Def." to be the same as when using "\Cref{a-def-in-my-work}".
@AlanMunn I haven't listened to her stuff that much. Simply put if you start down at the bass end of the vocal spectrum and continue upwards the higher you get the less interested I am in listening to it :þ
@StefanKottwitz @JosephWright @MartinScharrer hi buddies! Just wanted to introduce myself, I am the new CM! and I was wondering if there is any chat for the mods, would like to speak to you regarding the site. =))))
@PauloCereda Hi Paulo!!! How you doing today? Hope you are having a good one
@DavidCarlisle -- I see a CTAN update to .*-dev has been posted, with updates reported in ltnews34. That's currently very incomplete, so almost not worth reading (although infested with typos). But two questions: (1) will it be complete by October 15, to be included in the next TUGboat issue? And (2) does it include an update that fixes the mispositioning of captions with amsart? I looked quickly for that but didn't find it. Has that change been made yet?
The LaTeX Team submitted updates to the latex-base-dev, latex-amsmath-dev, latex-tools-dev, latex-graphics-dev, latex-firstaid-dev bundles.
Version: 2021-11-15 pre-release 2, except latex-firstaid-dev, which is v.1.0o 2021-06-28
TUG could announce what wasn't updated from L3. :)
@UlrikeFischer Is it enough if non-user actions support an attr option to add arbitrary text to the action dictionary or is there some need for more direct support?
@MarcelKrüger well the pressing part is the creating of the destination, so the \pdfdest name {ZZZ} obj 40 fit extension. An extension of \pdfstartlink is not really needed, but if it is done its main purpose would be to give a warning if the named structure destination doesn't exist, so an arbitrary text doesn't make sense (I could do that already).
@UlrikeFischer I assumed that the destination can be created manually and a warning would be rather unnecessary since the will always be a corresponding regular destination which will be warned about, so having a warning for the structured one would be redundant. Am I missing something?
(The idea of having arbitrary text there is to warn based on the regular destination(which doesn't work with user AFAICT) while still allowing to add the structured stuff.)
@MarcelKrüger well one naturally can create a destination manually, but then I have problems to get the coordinates for the XYZ type, FitR type etc., and I can't create named destinations.
@UlrikeFischer Since PDF doesn't have native support for named structured destinations, engine supported named destinations would be on the same level as ones emulated through macros. But anyway, I'll look into implementing it.
@MarcelKrüger hm you are right. the SD key expects an array, so probably you can't use named destinations. But it still remains the problem with FitR and XYZ. I don't want to restrict them to Fit.
@UlrikeFischer no been out this evening just got back. Well I have an idea the output routine gets switched but on its first call it just outputs the previous page not the expected start of table so it adds the tablehead at the top of the page on its second call but that comes above the section heading before the table.
@barbarabeeton yes we rushed that fix through so it just made it (with minutes to go:-) into that dev release.
@barbarabeeton teh dev releases are currently claiming a nominal release date of LaTeX2e <2021-11-15> pre-release-2 so not by October 15
@DavidCarlisle -- Okay, thanks. Please keep us posted. If there's a delay for the issue, squeaking it in may just be possible. Or if that's not possible, a pre-release notice can be included in my "news" column.