From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Filter for inline syntax extensions
Date: Mon, 14 Nov 2022 08:38:57 +0100 [thread overview]
Message-ID: <87r0y6561e.fsf@zeitkraut.de> (raw)
In-Reply-To: <b1e8933e-04eb-47b7-9cbb-2a5a58ea51c5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Hi Laurent,
Laurent Duperval <lduperval-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> I'm using the highlight.lua approach from here (https://
> gist.github.com/tarleb/a0646da1834318d4f71a780edaf9f870) and it works
> when exporting to PDF but not when exporting to ODT or DOCX. I'm not
> sure why. I would relly like a way to make this work reliably with
> ODT.
This depends on the pandoc writers for each format. As noted in my
original message, support for other formats requires more work.
The additional work to get support for ODT and docx is rather minimal
though: change lines 27-29 to
local function markup_inlines (inlines)
local attr = {class='mark', ['custom-style']='Highlighted'}
return pandoc.Span(inlines, attr)
end
The text can then be style via the 'Highlighted' character style.
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
next prev parent reply other threads:[~2022-11-14 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 8:57 Albert Krewinkel
[not found] ` <87edyle8l2.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-13 21:55 ` Laurent Duperval
[not found] ` <b1e8933e-04eb-47b7-9cbb-2a5a58ea51c5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-14 7:38 ` Albert Krewinkel [this message]
[not found] ` <87r0y6561e.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-11-14 14:29 ` Laurent Duperval
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0y6561e.fsf@zeitkraut.de \
--to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/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.
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 NNTP newsgroup(s).