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: How can I use figure placement specifiers with Markdown, e.g. [p] for special place?
Date: Sun, 24 Jul 2022 06:57:42 -0700 (PDT)	[thread overview]
Message-ID: <b4e6a305-f42f-4de3-8acc-4cebf83ed9ebn@googlegroups.com> (raw)


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

Hello!

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). 

\begin{figure}[p]
\includegraphics[width=\linewidth]{../assets/img/nf-rewards-2-alert.png}
\caption{An alert protocol's electrode location (left)...}
\label{fig:nf-alert}
\end{figure}

This works: 

![An alert protocol's electrode location (left) 
....](../assets/img/nf-rewards-2-alert.png){#fig:nf-alert}

But I'd like to keep the [p] in for when I make PDFs. 

The terminal says this: 

Undefined cross-reference: fig:nf-alert

Thanks! 

k

-- 
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/b4e6a305-f42f-4de3-8acc-4cebf83ed9ebn%40googlegroups.com.

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

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

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=b4e6a305-f42f-4de3-8acc-4cebf83ed9ebn@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).