public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Pranesh Prakash <the.solipsist-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Workflow for Markdown -> DOCX -> Markdown (with tracked changes)
Date: Thu, 12 Jan 2023 16:42:13 +0530	[thread overview]
Message-ID: <CAPD_o+8vK93Tk5kh=QLwTJt_-AkFN4bsbm9QSXGLGrQNL+O+QA@mail.gmail.com> (raw)

Dear all,
Recently, I wrote a paper with extensive citations (more than a
hundred footnotes) in Pandoc-flavoured Markdown, using Zotero for
reference management and an exported CSL YAML file.

To interact with the reviewers and copy-editors, I had to produce a
DOCX version.  They added comments, and suggested changes via tracked
changes.  I accepted many of the changes suggested, rejected some, and
made various other changes.  I now have a final DOCX version.

From that final DOCX version, I would like to produce:
1.  a final Mardown version
2.  a diff between my draft Markdown version and the final Markdown version
3. a publishable PDF version using pandoc (rather than LibreOffice)

I can generate a Markdown file from the final DOCX version, but that
doesn't preserve the original Markdown citations as @-citations, but
renders them as text footnotes.

I'm sure it's a common workflow, so how do other people deal with this?

Regards,
Pranesh


             reply	other threads:[~2023-01-12 11:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 11:12 Pranesh Prakash [this message]
     [not found] ` <CAPD_o+8vK93Tk5kh=QLwTJt_-AkFN4bsbm9QSXGLGrQNL+O+QA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-01-13 12:41   ` E. Castedo Ellerman

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='CAPD_o+8vK93Tk5kh=QLwTJt_-AkFN4bsbm9QSXGLGrQNL+O+QA@mail.gmail.com' \
    --to=the.solipsist-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).