public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "E. Castedo Ellerman" <castedo-HtDYFTekaG5BDgjK7y7TUQ@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Workflow for Markdown -> DOCX -> Markdown (with tracked changes)
Date: Fri, 13 Jan 2023 04:41:41 -0800 (PST)	[thread overview]
Message-ID: <d24811ff-6ad4-4110-a402-a1ed5ffdc05dn@googlegroups.com> (raw)
In-Reply-To: <CAPD_o+8vK93Tk5kh=QLwTJt_-AkFN4bsbm9QSXGLGrQNL+O+QA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2274 bytes --]

I suspect the common markdown workflow is to merge and track changes as one 
does with software source code, and not via Word. But I'm a software 
developer so I might be biased. More specifically, this workflow is to keep 
the markdown as the source-of-truth, use version control software like git, 
and merge each and every change back into the markdown as soon as possible 
(with git) and not after an extended period of changes managed by Word.

Halie Rando might have some advice and this thread might be of interest 
(you can find their contact info via the thread and github):

https://github.com/manubot/rootstock/issues/226

Sorry I don't have an easy solution to share. Overall it sounds like a bad 
situation you've gotten yourself into, sorry to say.
On Thursday, January 12, 2023 at 6:12:28 AM UTC-5 the.so...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:

> 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
>

-- 
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/d24811ff-6ad4-4110-a402-a1ed5ffdc05dn%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2959 bytes --]

      parent reply	other threads:[~2023-01-13 12:41 UTC|newest]

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

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=d24811ff-6ad4-4110-a402-a1ed5ffdc05dn@googlegroups.com \
    --to=castedo-htdyftekag5bdgjk7y7tuq@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).