From: Laurent Duperval <lduperval-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Filter for inline syntax extensions
Date: Sun, 13 Nov 2022 13:55:56 -0800 (PST) [thread overview]
Message-ID: <b1e8933e-04eb-47b7-9cbb-2a5a58ea51c5n@googlegroups.com> (raw)
In-Reply-To: <87edyle8l2.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1463 bytes --]
HI,
I know this message is pretty old but is there a place where I can find
this extension and how it works?
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.
Thanks,
L
On Saturday, July 16, 2022 at 5:00:01 AM UTC-4 Albert Krewinkel wrote:
> I've been playing around with a filter that adds additional markup
> syntax. In my example it uses `==highlight==` to add highlighted text.
> Highlighted (`mark`ed) text is only supported with HTML output, support
> for other formats would need some extra work.
>
> The filter comes with all the downsides of adding a second parsing step,
> but it works well in most cases. It can also be modified to support
> different markup.
> <https://gist.github.com/tarleb/a0646da1834318d4f71a780edaf9f870>
>
> --
> Albert Krewinkel
> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>
--
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/b1e8933e-04eb-47b7-9cbb-2a5a58ea51c5n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2433 bytes --]
next prev parent reply other threads:[~2022-11-13 21:55 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 [this message]
[not found] ` <b1e8933e-04eb-47b7-9cbb-2a5a58ea51c5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-11-14 7:38 ` Albert Krewinkel
[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=b1e8933e-04eb-47b7-9cbb-2a5a58ea51c5n@googlegroups.com \
--to=lduperval-re5jqeeqqe8avxtiumwx3w@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).