public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
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: Sun, 24 Jul 2022 08:17:48 -0700 (PDT)	[thread overview]
Message-ID: <0a6a41d3-fb62-43e9-a85e-edb09e53dc79n@googlegroups.com> (raw)
In-Reply-To: <87czdud1v5.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2151 bytes --]

Thanks Albert, 

You recommendations added the figure, but the cross referencing didn't come 
through:

1. there is no figure number before the figure's caption 
2. there is no reference in the text to the figure either, only : "(Fig. 
*¿fig:nf-alert?*)"

As the Terminal still says: 

Undefined cross-reference: fig:nf-alert

, this has probably something to do with using pandoc-crossref.

This is my line of code for making the file: 

% pandoc -F pandoc-crossref myOutput.md -o myOutput.docx 
--resource-path=../assets/img/ --citeproc --number-sections 
--lua-filter=parse-latex.lua

Thanks! 

// I can live with changing the the figure's Latex code to Markdown when I 
export to Word (it does not happen that often) 


On Sunday, July 24, 2022 at 3:25:27 PM UTC+1 Albert Krewinkel wrote:

>
> 'Krisztián Hofstädter' via pandoc-discuss <pandoc-...@googlegroups.com> 
> writes:
>
> > How can I use figure placement specifiers with Markdown, e.g. [p] for
> > special place?
> >
> > When converting from Markdown to PDF the figure with the code below is
> > rendered properly, however it is missing when converting to Word
> > (docx).
>
> The easiest way is probably to use the LaTeX code in combination with a
> Lua filter that parses the LaTeX when converting to a different output
> format:
>
> ``` lua
> if FORMAT:match 'latex' then return {} end
>
> function RawBlock (raw)
> if raw.format:match 'tex' then
> return pandoc.read(raw.text, 'latex').blocks
> end
> end
> ```
>
> Save the above to a file `parse-latex.lua` and pass it to pandoc via
> `--lua-filter=parse-latex.lua`.
>
> -- 
> 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/0a6a41d3-fb62-43e9-a85e-edb09e53dc79n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3039 bytes --]

  parent reply	other threads:[~2022-07-24 15:17 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 [this message]
     [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

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=0a6a41d3-fb62-43e9-a85e-edb09e53dc79n@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).