From: Mitch Wagner <mitch-lqILDgmZi8BBDgjK7y7TUQ@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Obsidian Pandoc plugin—Pandoc export failed
Date: Mon, 13 Nov 2023 10:10:42 -0800 (PST) [thread overview]
Message-ID: <449e0f8c-0488-4291-a2b6-ef916c422ca5n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 848 bytes --]
Hello, everyone! I'm using the Pandoc plugin for Obsidian on the Mac,
attempting to export a Markdown document to DOCX format. It works great
when I'm exporting a document that only contains text, but it fails when
I'm exporting a document containing text and embedded images. I've attached
the error message.
How can I export to DOCX with embedded images? I'm wondering whether
converting the images to JPGs might help.
Thanks!
--
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/449e0f8c-0488-4291-a2b6-ef916c422ca5n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1181 bytes --]
[-- Attachment #2: 7830CE8C-D005-40BC-8262-4CA6ECABA5E9.png --]
[-- Type: image/png, Size: 26612 bytes --]
next reply other threads:[~2023-11-13 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-13 18:10 Mitch Wagner [this message]
[not found] ` <449e0f8c-0488-4291-a2b6-ef916c422ca5n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-11-13 19:51 ` John MacFarlane
[not found] ` <2D789519-42C2-4193-9928-7DB0F5B177DD-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-11-14 0:48 ` Mitch Wagner
[not found] ` <9736ab3a-10eb-4a98-903c-c28e54366c76n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-11-14 10:36 ` Daniel Littlewood
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=449e0f8c-0488-4291-a2b6-ef916c422ca5n@googlegroups.com \
--to=mitch-lqildgmzi8bbdgjk7y7tuq@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).