From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ken Mankoff Subject: Re: Organizing and taming hectic Academia work (faculty viewpoint)? Tips or a good guides sought after :) Date: Fri, 12 Jun 2015 10:02:50 -0400 Message-ID: References: <7e093509.51e.14ddb300091.Coremail.chxp_moon@163.com> <161f0a5020b2f36c40a1e82a8af79089.squirrel@webmail.hafro.is> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37562) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z3PXw-0003iv-C1 for emacs-orgmode@gnu.org; Fri, 12 Jun 2015 10:03:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z3PXq-0000uC-OG for emacs-orgmode@gnu.org; Fri, 12 Jun 2015 10:03:00 -0400 Received: from mail-vn0-x22e.google.com ([2607:f8b0:400c:c0f::22e]:43343) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z3PXq-0000u8-KY for emacs-orgmode@gnu.org; Fri, 12 Jun 2015 10:02:54 -0400 Received: by vnbg7 with SMTP id g7so6134149vnb.10 for ; Fri, 12 Jun 2015 07:02:53 -0700 (PDT) In-reply-to: <161f0a5020b2f36c40a1e82a8af79089.squirrel@webmail.hafro.is> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Julian Burgos Cc: Holger Wenzel , emacs-orgmode , windy , John Kitchin Hi Julian, On 2015-06-10 at 10:16, Julian Burgos wrote: > a) I first write in org-mode. Export to Word, either exporting first > to ODT and then to Word, or to LaTex and then use pandoc to convert > LaTex to Word. My coauthor can edit the document as he wishes, using > the "Track changes" option. Then, I transcribe their edits back into > the org-mode document. Advantage of this approach: your coauthor > receives a clean word file, that could include figures, references, > etc., and he/she uses the tools she likes to edit the file. > Disadvantage: you have to manually incorporate the changes to the > org-mode file each time there are edits. > > b) I write the manuscript in org-mode. Then I send the org-mode file > to my coauthor. Because the org-mode file is just a text file, my > coauthor can use Word to edit it. I ask him/her *not* to use "track > changes" and to save the edited version also as a text file. Then, > when I receive it I use ediff in emacs to compare both documents and > incorporate the edits I want. Advantage of this approach: the merging > of the documents is easy using ediff. Disadvantage: your coauthor has > to edit a weird-looking document, with markup, code blocks, etc. It seems like with a bit of extra (scriptable?) work you could remove both disadvantages. Why can't you use method (a) above, and then DOCX -> Org via pandoc (with --accept-all option)? I know pandoc introduce some of its own changes to the Org syntax but not the document itself. You can get around this. You can remove the pandoc-generated changes automagically so that only co-author changes appear in Org format, which you can then use with your (b) above and emacs ediff. Original: Your Org source A: Org -> DOCX for co-authors (using pandoc) B: Org -> DOCX -> Org (using pandoc). C: A -> Org (using pandoc and --accept-all-changes) D: B-Original The difference between B and Original are pandoc-introduced changes that you do not want. Ignore/remove these changes from C, call it D and then the difference between D and the Original are your co-author comments. Now your authors can edit DOCX with Track Changes and you can work on those edits with Emacs ediff. -k.