-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues with microtype #4
Comments
20+ years ago the comment
was added to this package.... It is possible that now we could use the general LaTeX command hook mechanism to add code here rather than re-writing Notably here footmisc as well as microtype wants to adjust this command. @FrankMittelbach may have a view here as he's been looking at footnotes recently. |
This is only solvable well through a joint effort. Plan of attack:
The setspace overwrites are of the type "hook", ie there it just needs a suitable hook in the new code to allow such additions. My guess (but I have not checked) is that microtype has a similar need to configure what happens inside \footins and perhaps other parts --- this would need input from @schlcht to ensure that the right kind of hooks are enabled/offered. All that will show up first only in the -dev release and probably and from my timeline initially not in 2022-06 but only in latex-lab code there (ie only activated if \DocumentMetadata is used). Once properly tested it could then move into main in Fall and footmisc, setspace, microtype, ... could start using hooks rather than overwriting each other. |
The reason why microtype fails to apply its footnote patch is only because in the example document setspace is loaded after hyperref: microtype includes a dedicated footnote patch for hyperref, but the hyperref definition is overwritten by setspace (which microtype isn't aware of). There would be no problem if hyperref were loaded after setspace (which is also common advice) or not at all. So I would say the problem lies with setspace for blindly overwriting Regarding hooks in @footnotetext, I suspect the ship has sailed long ago. Grepping for \def@footnotetext in my (quite incomplete) texlive already yields two dozen redefinitions, all of which would have to be amended for the hook to be really usable. But just for the record, what microtype would need would be a hook just before the actual footnote text, so between |
I understand that until the situation is completely fixed through the joint effort illustrated above, users should be careful in loading I assume that in this way one shall get the |
hyperref saves (and calls) the version current at the point of its patch as
you see it calls the
|
we have to clean up these kind of things if we want to keep LaTeX useful. Tagging will never work otherwise and anyway this constant overwriting becomes more and more a nightmare. In that particular case it isn't too bad (I just went through the whole of TL and checked) and in any case unconditional overwrites always break stuff, you can't make all packages the last one, so mid term hooks instead of overwrites are the only sensible way in my opinion and such packages then need to follow or tough ... some newer features aren't available (or vanish). With a bit of goodwill that should work and it would be transparent to users. |
The new footnote support contains hooks that can deal with this issue but it will take probably one or two LaTeX releases before this will be generally available. |
Looks like using
setspace
together withmicrotype
makes it impossible for the latter to patch thefootnote
command as it would like.Issue has also been opened for the microtype package. schlcht/microtype#11
The text was updated successfully, but these errors were encountered: