From: Manuel Koell <man.koell@gmail.com>
To: Vikas Rawal <vikaslists@agrarianresearch.org>
Cc: Pascal Fleury <fleury@google.com>,
org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: A book produced using Org
Date: Sun, 20 Sep 2015 04:40:38 +0200 [thread overview]
Message-ID: <CAAAbm0oMWhitDaqXx02_Rv5f4ohQ=CRb6Uc+BUR_qBMXVsztVA@mail.gmail.com> (raw)
In-Reply-To: <6F8ECF8A-D17C-4A27-878B-D0C98E064C77@agrarianresearch.org>
[-- Attachment #1: Type: text/plain, Size: 2488 bytes --]
Beautiful! I would love to see the org file! How did emacs perform which
such huge file?
2015-09-20 3:06 GMT+02:00 Vikas Rawal <vikaslists@agrarianresearch.org>:
>
> > On 20-Sep-2015, at 4:20 am, Pascal Fleury <fleury@google.com> wrote:
> >
> > Great! Congrats!
> >
> > I was actually wondering: you are 3 authors. How did you collaborate, in
> practice ? There was a thread about using org for collaborative work, but
> it seemed to end in discussing other tools...
> > Was it plain git/emacs and the tools used usually for code management ?
>
>
> Well, unfortunately, the other two authors are not familiar with emacs,
> org-mode, or LaTeX.
>
> The parts they wrote were sent as MS-Word files. I converted them into
> Org-mode.
>
> For the parts I wrote, I sent them PDFs. The first time, I also sent them
> a Word version. I offered them that they could comment in word (with track
> changes) and send me, or better still, work on hard copies and send me the
> scans. The PDFs were so far superior to those word files, that could not
> resist them :). So, their comments came as scans of the commented hard
> copies, and I incorporated them in. Once they were comfortable with this,
> in subsequent rounds, I had to send them only PDFs.
>
> We followed the same process with the copy editors. The copy editors
> worked on hard copies, and I incorporated the comments. This actually had a
> huge advantage since, in the process of incorporating their edits, I went
> through every single change they wanted to make. I do not know if they had
> done this on their software, how I would have gone through every sentence
> to check if and what had been modified.
>
> The publisher usually works with InDesign, but was willing to let me deal
> with production of the print-ready PDF if I could meet her specifications.
> Again, this meant additional work for me. But this was also far more
> efficient than converting everything into Word, and then letting her set it
> up on InDesign. Both these steps would have been far more laborious. For
> example, I doubt if InDesign can make an author index automatically from
> citations in the way biblatex does.
>
> So, the barrier in our case was not to find the most appropriate
> version-control software. The problem was that the other two authors were
> completely unfamiliar with any of these tools. But, even with that, using
> Org-mode was so far superior to shifting to Word or anything of that kind.
> No question.
>
> Vikas
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 2954 bytes --]
next prev parent reply other threads:[~2015-09-20 2:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-19 22:26 A book produced using Org Vikas Rawal
2015-09-19 22:38 ` Fabrice Popineau
2015-09-20 0:01 ` Thomas S. Dye
[not found] ` <CACc7+8Yz5dz2cNKqpCoyOT3Arz8DwzrfYcXAUZ9f1NUMftrZAg@mail.gmail.com>
2015-09-20 1:06 ` Vikas Rawal
2015-09-20 2:40 ` Manuel Koell [this message]
2015-09-20 5:09 ` Vikas Rawal
2015-09-20 6:50 ` Rainer M Krug
2015-09-20 12:50 ` Suvayu Ali
2015-09-21 14:39 ` Vikas Rawal
2015-09-20 23:27 ` John Kitchin
2015-09-20 9:02 ` Martin Schöön
2015-09-21 14:32 ` Vikas Rawal
2015-09-21 19:51 ` Grant Rettke
2015-09-21 22:50 ` Suvayu Ali
2015-09-22 11:23 ` Rasmus
2015-09-21 23:43 ` Vikas Rawal
2015-09-22 0:25 ` Grant Rettke
2015-09-20 7:29 ` Detlef Steuer
2015-09-20 13:13 ` M
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAAbm0oMWhitDaqXx02_Rv5f4ohQ=CRb6Uc+BUR_qBMXVsztVA@mail.gmail.com' \
--to=man.koell@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=fleury@google.com \
--cc=vikaslists@agrarianresearch.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).