From: "Jan Stühler" <jan.stuehler-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: docx with images in tables to markdown and back
Date: Fri, 21 Oct 2022 05:30:17 -0700 (PDT) [thread overview]
Message-ID: <02f65a26-e99a-4cfb-9ef7-899e7f40f899n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1468 bytes --]
Hello group.
I use
```
pandoc -f docx -t markdown --extract-media "Lab 1-2.docx-dir" -o file.md
file.docx
```
to convert a word document to markdown. The word document has (many) images
which are sitting in table cells. One of the results is:
```
1
+===============================+======================================+
2 | Click on the Link:\ | ![](./Lab 1-2.docx-dir/media/ima
|
3 | *[Click here to start the | ge7.png){width="3.643961067366579in"
|
4 | Local Service | height="1.9991174540682415in"}
|
```
(Line numbers from `vim`).
Observe the line break between `ima` and `ge7.png`.
To convert this markdown to word, I use
```
pandoc -f markdown -t docx -o file-new.docx file.md
```
which results in this error message:
```
[WARNING] Could not fetch resource
./Lab%201-2.docx-dir/media/ima%20ge7.png: replacing image with description
```
Observe the `%20` between `ima` and `ge7.png`.
Is there something I can do so that pandoc can put the images into the word
document?
Thanks alot.
--
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/02f65a26-e99a-4cfb-9ef7-899e7f40f899n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2195 bytes --]
next reply other threads:[~2022-10-21 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 12:30 Jan Stühler [this message]
[not found] ` <02f65a26-e99a-4cfb-9ef7-899e7f40f899n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-21 16:16 ` John MacFarlane
[not found] ` <C16FAB55-4036-460E-A3CA-5C755EB2F207-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-22 18:56 ` Jan Stühler
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=02f65a26-e99a-4cfb-9ef7-899e7f40f899n@googlegroups.com \
--to=jan.stuehler-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).