From: "András Simonyi" <andras.simonyi@gmail.com>
To: "András Simonyi" <andras.simonyi@gmail.com>,
"Ihor Radchenko" <yantar92@posteo.net>,
emacs-orgmode@gnu.org
Subject: Re: [PATCH][oc-csl] Improve reference parsing
Date: Thu, 19 Jan 2023 10:35:35 +0100 [thread overview]
Message-ID: <CAOWRwxB7iJW+T4WMByz48BdKH3phQKKX=JToomYJMNoq04vOJg@mail.gmail.com> (raw)
In-Reply-To: <87wn5isz00.fsf@guelker.eu>
Dear All,
On Thu, 19 Jan 2023 at 09:35, M. ‘quintus’ Gülker
<post+orgmodeml@guelker.eu> wrote:
> 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.
hopefully somebody more knowledgeable than me can comment on how
viable this is, but would a @@csl like export snippet construct help
with the problem?
In that case your macro could be along the lines of
#+MACRO: name @@csl:<span style="font-variant: small-caps">$1</span>@@
and -- assuming the custom export backend approach I proposed in the
patch -- we would only need to make sure that the inline @@csl export
snippets are exported as is by this "csl" backend.
best wishes,
András
next prev parent reply other threads:[~2023-01-19 9:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 15:40 [PATCH][oc-csl] Improve reference parsing András Simonyi
2022-10-27 4:10 ` Ihor Radchenko
2022-11-01 15:02 ` András Simonyi
2022-11-02 6:29 ` Ihor Radchenko
2022-11-02 17:58 ` András Simonyi
2022-11-03 6:34 ` Ihor Radchenko
2023-01-07 12:50 ` M. ‘quintus’ Gülker
2023-01-15 8:56 ` Ihor Radchenko
2023-01-18 23:08 ` András Simonyi
2023-01-19 8:21 ` M. ‘quintus’ Gülker
2023-01-19 9:35 ` András Simonyi [this message]
2023-01-19 9:59 ` Ihor Radchenko
2023-01-19 10:11 ` M. ‘quintus’ Gülker
2023-01-25 22:44 ` András Simonyi
2023-01-19 9:56 ` Ihor Radchenko
[not found] ` <CAOWRwxD3pSfao7+G145naE=jaAz6=m2BjvUX0rj_c4r8qeu7rQ@mail.gmail.com>
2023-01-26 9:43 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOWRwxB7iJW+T4WMByz48BdKH3phQKKX=JToomYJMNoq04vOJg@mail.gmail.com' \
--to=andras.simonyi@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).