public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Michael Becker <michael-QF1XyMwE1Uwv0rdu9s6TydBPR1lH4CV8@public.gmane.org>
To: pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
	John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
Subject: Re: Extract Images from Markdown to Docx
Date: Sun, 12 Sep 2021 09:38:47 -0700	[thread overview]
Message-ID: <7b04a65e-ba3a-48f6-abce-1532c47b90a4@Spark> (raw)
In-Reply-To: <m2lf41zu2l.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2604 bytes --]

Thank you. Found the error.  I your approach to break it into a smaller file helped. Was missing a tag.


Michael J. Becker
CEO
Identity Praxis, Inc.
michael-QF1XyMwE1Uwv0rdu9s6TydBPR1lH4CV8@public.gmane.org
M: +1-408-242-5733
https://www.linkedin.com/in/privacyshaman/

Check my availability & schedule meeting with me: 30 MIN or 60 MIN
On Sep 12, 2021, 8:34 AM -0700, John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>, wrote:
>
> You shouldn't use --extract-media for md -> docx (but do use it for the
> reverse conversion). For md -> docx it should just work.
> But there are some complexities if e.g. your markdown files
> are not in the directory where you're using the pandoc command.
> (See the manual under rebase_relative_paths: you could try
> with `-f markdown+rebase_relative_paths` to se if that helps.)
>
> If you want help with this, the best thing is to create a zip
> file with everything needed to reproduce the problem (a markdown
> document, as short as possible, and the images you're using),
> together with the exact command you're using.
>
>
> Michael Becker <michael-QF1XyMwE1Uwv0rdu9s6TydBPR1lH4CV8@public.gmane.org> writes:
>
> > Hi there, I'm on a Mac M1 min. Have pandoc 2.14.2 installed. I'm trying to
> > convert a .mb to .docx file. The file converts fine, but the images are not
> > getting extracted. The .md file renders the images just fine. Something is
> > clearly wrong with my extraction path "
> >
> > " --extract-media=media"" but I can't figure it out. I've tried various
> > combinations of this
> >
> > --extract-media=/Users/myname/pandocSP/media/
> > --extract-media=/media
> >
> >
> > Does anyone have any tips on how I can debug this?
> >
> >
> > Michael
> >
> > --
> > 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/587134c4-83b5-4983-b329-3f3c1da7913dn%40googlegroups.com.

-- 
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/7b04a65e-ba3a-48f6-abce-1532c47b90a4%40Spark.

[-- Attachment #2: Type: text/html, Size: 4989 bytes --]

      parent reply	other threads:[~2021-09-12 16:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-12 14:51 Michael Becker
     [not found] ` <587134c4-83b5-4983-b329-3f3c1da7913dn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-12 15:34   ` John MacFarlane
     [not found]     ` <m2lf41zu2l.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-09-12 16:38       ` Michael Becker [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=7b04a65e-ba3a-48f6-abce-1532c47b90a4@Spark \
    --to=michael-qf1xymwe1uwv0rdu9s6tydbpr1lh4cv8@public.gmane.org \
    --cc=jgm-TVLZxgkOlNX2fBVCVOL8/A@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).