From: "Mert.Kara" <mertkarracan96-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Converting several markdown files into docx
Date: Wed, 1 Feb 2023 05:56:24 -0800 (PST) [thread overview]
Message-ID: <e07223da-8f56-4f14-86f5-b8d5a0de461cn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1505 bytes --]
I have a folder called Project:
Project:
img docs README
The README is written in Markdown and looks like this:
document 1
document 1.1
document 2
document 2.1
document 2.1.1
The readme has links to the individual Markdown files. The file structure
in the document folder looks like this:
Document 1
Document 2
Document 11
Document 21
Document 211
The documents have images that come from the img folder and have cross
references to each other e.g. Document 1 has a reference to Document 11.
How can I use a pandoc command to convert the documents as they appear in
order in the README to a DOCX file, with the corresponding images and the
cross references in the respective Markdown files. Is there a suitable
script with pandoc for this?
I had it once with the pandoc command:
for /r "." %i in (*.md) do pandoc -o "%~i.docx" "%~i"
All files in the docs folder were converted to a DOCX file and merged, but
the order was completely wrong and the cross references were to the
Markdown files from the docs folder and not from the created DOCX file.
--
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/e07223da-8f56-4f14-86f5-b8d5a0de461cn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1918 bytes --]
reply other threads:[~2023-02-01 13:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e07223da-8f56-4f14-86f5-b8d5a0de461cn@googlegroups.com \
--to=mertkarracan96-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).