public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Adarsh Balachandran
	<adarshbm11-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pandoc docx output missing images
Date: Sun, 23 May 2021 13:15:48 -0700	[thread overview]
Message-ID: <m2wnrpp5or.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <CAFf_abOuTwMLMUVaMLHzbN60VOg1_p-GA=18T3ixCWLd5JG_nw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


These are svg images, and if I recall we don't yet support these
for docx:
https://github.com/jgm/pandoc/issues/4058
(We target an older version of docx for compatibility, and
SVG capability was only added in Word 2016.  The linked issue
suggests converting to png for the docx, which we could do.)

Adarsh Balachandran <adarshbm11-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> When converting a webpage generated by mkdocs material theme
> <https://squidfunk.github.io/mkdocs-material/reference/images/>, images are
> missing from the Pandoc output.
>
> Please see below the conversion command and the pandocTheme.docx url:
> *pandoc --reference-doc pandocTheme.docx -f html -t docx -o myDoc.docx
> https://squidfunk.github.io/mkdocs-material/reference/images/
> <https://squidfunk.github.io/mkdocs-material/reference/images/>*
>
> https://pandoc.org/demo/twocolumns.docx
>
> Thanks and regards,
> Adarsh Balachandran
> *Mob*: +91 9895792641
>
> -- 
> 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/CAFf_abOuTwMLMUVaMLHzbN60VOg1_p-GA%3D18T3ixCWLd5JG_nw%40mail.gmail.com.


  parent reply	other threads:[~2021-05-23 20:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-23 19:47 Adarsh Balachandran
     [not found] ` <CAFf_abOuTwMLMUVaMLHzbN60VOg1_p-GA=18T3ixCWLd5JG_nw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-05-23 20:15   ` Albert Krewinkel
2021-05-23 20:15   ` John MacFarlane [this message]
2021-06-30 23:41 Paul Evans
     [not found] ` <CAE4RJyCwfz-3NDcVq=W2x-SpwgW2wq_HVtKAw=ZYnuAAVDvFLQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-07-01  0:30   ` John MacFarlane
     [not found]     ` <yh480k7diaswni.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-07-01  0:50       ` Paul Evans
     [not found]         ` <83d81b83-1a29-4f02-b2c3-3652222f141cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-01  9:44           ` gnpan
     [not found]             ` <55eedaaa-078d-4d00-ae06-4cf3892015c2n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-01 19:58               ` Paul Evans
2021-07-01  0:56   ` John MacFarlane

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=m2wnrpp5or.fsf@MacBook-Pro.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=adarshbm11-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).