From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.text.pandoc/31989 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "E. Castedo Ellerman" Newsgroups: gmane.text.pandoc Subject: Re: Workflow for Markdown -> DOCX -> Markdown (with tracked changes) Date: Fri, 13 Jan 2023 04:41:41 -0800 (PST) Message-ID: References: Reply-To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_6108_1680317773.1673613701327" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34442"; mail-complaints-to="usenet@ciao.gmane.io" To: pandoc-discuss Original-X-From: pandoc-discuss+bncBCDYLW6J6IFBBBVDQWPAMGQEF3FUFAY-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Fri Jan 13 13:41:46 2023 Return-path: Envelope-to: gtp-pandoc-discuss@m.gmane-mx.org Original-Received: from mail-oo1-f55.google.com ([209.85.161.55]) by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pGJNR-0008oC-TW for gtp-pandoc-discuss@m.gmane-mx.org; Fri, 13 Jan 2023 13:41:45 +0100 Original-Received: by mail-oo1-f55.google.com with SMTP id p10-20020a4a3c4a000000b004e21e7fb4e3sf7934157oof.3 for ; Fri, 13 Jan 2023 04:41:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20210112; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:reply-to:x-original-sender :mime-version:subject:references:in-reply-to:message-id:to:from:date :sender:from:to:cc:subject:date:message-id:reply-to; bh=q5dKXLRLOM1Vr+afxxk4yXxEH1rwnQfq+Xlx5f771OI=; b=SdgvuMXUo06qdm8h2kNXEqC0/krBqX5J1FvNDQj3hEbkgw13fmTLP9Cr0Q3NwdRFYU IaBq85PrxPARy8sc7UOhm7pQtm84zIPAeBfjaysQ4C3R9P/QpWv96jTEf9d7vE08UUZ0 4K/2kAhLxtBO1yBS4lqCoPdd28DMM0Baowzb4jBCcq5JT5BfYGU0HXuYpSYagxedEVY2 KJn2ss9ymF0Ggp56s6oaQ0qsyrvWF9Ey4yV0Ctz3K/guIhzi+APbjqHVo7/Bp9iWUYFt 8MY8E+xvnCVzsKyTEM0JHZCew8fGxneJxu1v/LVXPan6dmCSTx0Z2uIdJzw8QuGUKbvz 9K3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :x-spam-checked-in-group:list-id:mailing-list:precedence:reply-to :x-original-sender:mime-version:subject:references:in-reply-to :message-id:to:from:date:x-gm-message-state:sender:from:to:cc :subject:date:message-id:reply-to; bh=q5dKXLRLOM1Vr+afxxk4yXxEH1rwnQfq+Xlx5f771OI=; b=m5NkK/am3vSLWlV2+gdQ7sIRTq279mPEjGh0y25hYfxoEgkIZkyriBzRH+RoVOSfdy p3b9KhI/Iy7Hdna5Bs1W2crh8yg4u0nk5pWBTPzA/664a7hre4AVgaTYtbmB2hZj0+28 tqe39uPtK3btMC9CrdZLKbyWfNiQ9CDWpNuPsb254siO1NpbN9QbvbwYk6qEI5LzJkmO WKhSEZYS3IVqsOATX8T+i7I/yYgSVles6kkX2eqdrakyWQjC1h6Z3V0oP9s417/rMsQN Bgw6zXyTxyN4fyml1AGhFi5+EIYzu7kgLf5Tdy/MwU/YUFKDCG0mGkBymYbHSR7P9gG/ 1SYg== Original-Sender: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org X-Gm-Message-State: AFqh2kpMmnIenl0I5OxKzHx9oMxKyX2SEYBhM1GZ/cIwIYIquh55G2wv JVNpM6TB8FWG346xoa3M5d8= X-Google-Smtp-Source: AMrXdXu1j7Em6kYFQNJ425AU/tiKG6AVTP4i/UDqBA5bygaJmgXAOuN+Z85TNtw1mTQMmQzYYanhiA== X-Received: by 2002:a05:6808:2906:b0:35b:4508:3c80 with SMTP id ev6-20020a056808290600b0035b45083c80mr6778476oib.109.1673613704757; Fri, 13 Jan 2023 04:41:44 -0800 (PST) X-BeenThere: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org Original-Received: by 2002:a05:6870:b7b0:b0:151:dc85:d779 with SMTP id ed48-20020a056870b7b000b00151dc85d779ls2282240oab.6.-pod-prod-gmail; Fri, 13 Jan 2023 04:41:42 -0800 (PST) X-Received: by 2002:a05:6870:a92a:b0:15b:b07e:64c7 with SMTP id eq42-20020a056870a92a00b0015bb07e64c7mr1011616oab.166.1673613702088; Fri, 13 Jan 2023 04:41:42 -0800 (PST) In-Reply-To: X-Original-Sender: castedo-HtDYFTekaG5BDgjK7y7TUQ@public.gmane.org Precedence: list Mailing-list: list pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org; contact pandoc-discuss+owners-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org List-ID: X-Google-Group-Id: 1007024079513 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , Xref: news.gmane.io gmane.text.pandoc:31989 Archived-At: ------=_Part_6108_1680317773.1673613701327 Content-Type: multipart/alternative; boundary="----=_Part_6109_1943968970.1673613701327" ------=_Part_6109_1943968970.1673613701327 Content-Type: text/plain; charset="UTF-8" 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. ------=_Part_6109_1943968970.1673613701327 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I suspect the common markdown workflow is to merge and track changes a= s 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 possibl= e (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 threa= d 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 you= rself 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 ver= sion
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, bu= t
renders them as text footnotes.

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

Regards,
Pranesh

--
You received this message because you are subscribed to the Google Groups &= quot;pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to pand= oc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@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.
------=_Part_6109_1943968970.1673613701327-- ------=_Part_6108_1680317773.1673613701327--