From: Don Raikes <DON.RAIKES-MouhYhfBpPxXrIkS9f7CXA@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: problems with docx to markdown conversion
Date: Thu, 16 Apr 2020 13:59:50 -0700 (PDT) [thread overview]
Message-ID: <fa15044a-b72b-49be-85f4-d3d60bd58c6c@default> (raw)
[-- Attachment #1: Type: text/plain, Size: 2372 bytes --]
Hello,
Maybe there is a problem in my understanding or I my process, but I am struggling to effectively use pandoc in a writing project.
My process is:
I write my documents in markdown.
The documents include a lot of fenced code blocks both for html and javascript as well as example of interactive sessions in the terminal.
I convert my markdown files into docx files and send them to my editor.
She makes changes and sends the docx files back to me.
I convert the docx files back to markdown, but then I have to go in and fix all the fenced code blocks because they are not marked as fenced blocks any more. Plus I have to fix any embedded links and graphics because the code for those have gotten split over two lines and they will not convert back to docx unless I have gone through and joined the lines back together.
Based on the articles I have read about using pandoc for writing projects it doesn't seem like the process should be this difficult, so what am I doing wrong?
The commands I am using for conversion are:
Markdown to docx:
Pandoc -s -f markdown -t docx -o project.docx project.md
Docx to markdown:
Pandoc -s -f docx -t markdown -atx-headers -o project.md project.docx
Any pointers to make the process work better would be greatly appreciated.
--
Thanks, Donald
"As a leader, to be successful, is to help the people around you to be successful." - Kent Boucher
Accessibility, like security, is better when built-in from the beginning rather than bolted on at the end.
http://www.oracle.com/
Donald Raikes | Accessibility Specialist
Mobile: HYPERLINK "tel:+15202717608"+15202717608 | VOIP: HYPERLINK "tel:+15205744033"+15205744033
Oracle Accessibility Program Office
| Tucson, Arizona
http://www.oracle.com/commitment
Oracle is committed to developing practices and products that help protect the environment
--
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/fa15044a-b72b-49be-85f4-d3d60bd58c6c%40default.
[-- Attachment #2: Type: text/html, Size: 7828 bytes --]
next reply other threads:[~2020-04-16 20:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 20:59 Don Raikes [this message]
2020-04-16 23:16 ` John MacFarlane
2020-05-04 18:48 Don Raikes
2020-05-05 5:53 ` John MacFarlane
[not found] ` <m2tv0v3p1s.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-05-05 17:12 ` Don Raikes
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=fa15044a-b72b-49be-85f4-d3d60bd58c6c@default \
--to=don.raikes-mouhyhfbppxxriks9f7cxa@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).