From: Alan L Tyree <alantyree@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Organizing and taming hectic Academia work (faculty viewpoint)? Tips or a good guides sought after :)
Date: Wed, 17 Jun 2015 09:15:01 +1000 [thread overview]
Message-ID: <5580ADF5.6040402@gmail.com> (raw)
In-Reply-To: <87616obey5.fsf@bobnewell.net>
On 16/06/15 11:49, Bob Newell wrote:
> "Julian Burgos" <julian@hafro.is> writes:
>
>> 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.
> Simple is best, and I wish I had thought of this simple idea before I
> took an 87,000 word novel that I wrote in org-mode, output as ODT,
> converted to DOCX, and then sent to an editor. I got back all the track
> changes stuff and even worse, margin notes, and punctuation (like quotes
> and ellipses) changed over to Word-ish characters.
>
> It wasn't utterly useless but it created a lot of extra work, which
> still isn't over. Next time I'll do as per above, tell her to just edit
> the thing directly, write her notes in-line, and keep it as pure ASCII.
>
> I really believe she thinks I was going to use Word to publish the
> novel. Failure to communicate on my part. I could say lack of judgment
> on her part but that's unfair; in her world, most everyone uses Word at
> some stage in the process.
>
I used this method when working with an editor on the last edition of my
book on banking law: almost 300,000 words. I had a few special
constructs that I asked her not to meddle with, and she put editors
notes in-line. It worked a treat although the publisher actually
required Word files at the end.
Cheers,
Alan
--
Alan L Tyree http://www2.austlii.edu.au/~alan
Tel: 04 2748 6206 sip:typhoon@iptel.org
next prev parent reply other threads:[~2015-06-16 23:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 16:39 Organizing and taming hectic Academia work (faculty viewpoint)? Tips or a good guides sought after :) Xebar Saram
2015-06-08 21:16 ` M
2015-06-09 5:13 ` Xebar Saram
2015-06-09 7:00 ` Holger Wenzel
2015-06-09 13:21 ` John Kitchin
2015-06-10 1:57 ` windy
2015-06-10 13:49 ` John Kitchin
2015-06-10 14:14 ` Ken Mankoff
2015-06-10 20:58 ` Titus von der Malsburg
2015-06-11 5:30 ` Rasmus
2015-06-11 14:56 ` Phillip Lord
2015-06-11 17:02 ` John Kitchin
2015-06-12 13:24 ` Phillip Lord
2015-06-10 14:16 ` Julian Burgos
2015-06-11 2:07 ` windy
2015-06-11 5:38 ` Rasmus
2015-06-11 12:19 ` windy
2015-06-11 12:18 ` Ken Mankoff
2015-06-11 12:54 ` windy
2015-06-12 14:02 ` Ken Mankoff
2015-06-13 19:06 ` Xebar Saram
2015-06-13 19:52 ` John Kitchin
2015-06-15 17:33 ` Julian Burgos
2015-06-16 1:49 ` Bob Newell
2015-06-16 23:15 ` Alan L Tyree [this message]
2015-06-10 18:51 ` Eric S Fraga
2015-06-09 9:49 ` Alan Schmitt
2015-08-26 14:17 ` Anders Johansson
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=5580ADF5.6040402@gmail.com \
--to=alantyree@gmail.com \
--cc=emacs-orgmode@gnu.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).