Am Donnerstag, dem 19. Januar 2023 schrieb András Simonyi: > apologies for replying that late. If I understand the situation > correctly, we could handle the question of allowing macros in > citations independently of the handling of other constructs, because > macros are resolved before processing citations, so they have no > effect on the input of Citeproc-el. In light of this, maybe there > could be a separate patch for just allowing macros?
I am not sure this targets the usecase I am pursuing, which is to use macros to produce @@latex: escape constructs in order to have small-caps markup in the citation footnotes: #+MACRO: name @@latex:\textsc{$1}@@@@html:<span class="name">$1</span>@@ If the macro resolves, but the @@latex construct does not, that would be problematic. That being said, I /found/ an alternative that works, albeit it is a bit ugly. I can create an explicit footnote, use a [cite/default/bare:] construct (to suppress the terminal period) within it and terminate the citation before the macro begins. That way, the macro is outside of the citation construct. This construction is however unfortunate when I want to cite multiple sources and have the macro used on an earlier one, e.g.: [fn:1] [cite/default/bare:@foo p. 5], countering {{{name(Doe’s)}}} argument; [cite/default/bare:@bar p. 37]. It would be nicer if I could just write into the main text [cite:@foo p. 5, countering {{{name(Doe’s)}}} argument;@bar p. 37] I can however live with the more elaborate construction, if nothing else. -quintus -- Dipl.-Jur. M. Gülker | https://mg.guelker.eu | PGP: Siehe Webseite Passau, Deutschland | kont...@guelker.eu | O<