public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: TJ Schuler <schuler.tj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Extract media from Docx does not extract SVG files
Date: Fri, 23 Apr 2021 21:23:47 -0700	[thread overview]
Message-ID: <m2lf98qpik.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <262b736a-880f-405f-a58f-a4e20718607bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


If you're using an older version of pandoc, be sure to
try with the latest, and check the changelog.

But after doing that, I think filing an issue makes sense.

TJ Schuler <schuler.tj-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> I am running into an issue with Word files with SVG figures. My source word 
> files all have SVG files as figures, but pandoc seems to only extract the 
> PNG version of those figures that word uses for previews.  
>
> Any ideas on how to get around this issue in pandoc or should I file an 
> issue for it in GitHub?
>
> Thanks  --TJ
>
> -- 
> 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/262b736a-880f-405f-a58f-a4e20718607bn%40googlegroups.com.


      parent reply	other threads:[~2021-04-24  4:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-23 22:23 TJ Schuler
     [not found] ` <262b736a-880f-405f-a58f-a4e20718607bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-04-24  4:23   ` John MacFarlane [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=m2lf98qpik.fsf@MacBook-Pro.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=schuler.tj-Re5JQEeQqe8AvxtiuMwx3w@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).