From: "'Krisztián Hofstädter' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How can I use figure placement specifiers with Markdown, e.g. [p] for special place?
Date: Tue, 26 Jul 2022 02:55:43 -0700 (PDT) [thread overview]
Message-ID: <b7ff6d15-f0cc-4d97-9b14-91ea92218edfn@googlegroups.com> (raw)
In-Reply-To: <874jz5cvqx.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1591 bytes --]
Thanks Albert,
Unfortunately, none of the snippets above worked :(
The more conservative one removed the title pages as well.
Hmm... I will simply my files and test again!
Danke!! k
On Monday, July 25, 2022 at 11:49:51 AM UTC+1 Albert Krewinkel wrote:
>
> 'Krisztián Hofstädter' via pandoc-discuss <pandoc-...@googlegroups.com>
> writes:
>
> > Brilliant! Thanks Albert :-)
>
> You're welcome, happy it works 😊
>
> > Now that I'm on it, .... how could I also convert the Contents, List of
> > Figures and Tables when making the docx file?
> > (When converting to PDF they are all there.)
>
> The Lua filter is a bit too eager and also parses LaTeX blocks that
> should be consumed by pandoc-crossref. Try to modify it like this:
>
> ```
> if raw.format:match 'tex' and not raw.text:match '\\listof' then
> return pandoc.read(raw.text, 'latex').blocks
> end
> ```
>
> or, more conservatively
>
> ```
> if raw.format:match 'tex' and raw.text:match '\\begin%{figure%}' then
> return pandoc.read(raw.text, 'latex').blocks
> end
> ```
>
> --
> 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/b7ff6d15-f0cc-4d97-9b14-91ea92218edfn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2353 bytes --]
prev parent reply other threads:[~2022-07-26 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-24 13:57 'Krisztián Hofstädter' via pandoc-discuss
[not found] ` <b4e6a305-f42f-4de3-8acc-4cebf83ed9ebn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-24 14:20 ` Albert Krewinkel
[not found] ` <87czdud1v5.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-07-24 15:17 ` 'Krisztián Hofstädter' via pandoc-discuss
[not found] ` <0a6a41d3-fb62-43e9-a85e-edb09e53dc79n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-24 16:13 ` Albert Krewinkel
[not found] ` <878roicwo8.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-07-25 9:50 ` 'Krisztián Hofstädter' via pandoc-discuss
[not found] ` <1d05b65b-70c3-41f4-b4be-b1578db89f55n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-07-25 10:39 ` Albert Krewinkel
[not found] ` <874jz5cvqx.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-07-26 9:55 ` 'Krisztián Hofstädter' via pandoc-discuss [this message]
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=b7ff6d15-f0cc-4d97-9b14-91ea92218edfn@googlegroups.com \
--to=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).