From: Alan L Tyree <firstname.lastname@example.org>
To: David Rogers <email@example.com>
Cc: firstname.lastname@example.org, Jambunathan K <email@example.com>
Subject: Re: Index of cases
Date: Mon, 09 Sep 2013 08:55:33 +1000 [thread overview]
Message-ID: <522D0065.firstname.lastname@example.org> (raw)
On 09/09/13 08:17, David Rogers wrote:
> Jambunathan K <email@example.com> writes:
>> Jambunathan K <firstname.lastname@example.org> writes:
>>>> I have (I think) got them to agree to accept plain text, but I would
>>>> like to make it just as plain as possible.
>>> Oh, Ok. Looks like there is "exchange of ideas" between the author and
>> In lighter vein and tongue-in-cheek sort of way...
>> It seems like publishers are making you go in circles.
>> You were after epub. Now you are after Word. It is only a matter of
>> time, before a publisher insists on an LaTex, at which point you would
>> have done the full-circle and savour a moment of epiphany.
> I'm wondering something a bit different:
> It sounds as if the publisher actually demands Word documents, and had
> never asked for anything but that.
> I'm swallowing hard before I say this...
> Why not just use Word?
Well, the book is already in LaTeX. I chose that back at the 4th edition
and am now in the process of preparing the 8th. Earlier editions were in
Word, and the new Word can't even read the early manuscripts. I
regularly lost work using Word. The usual complaints.
I had special needs at the time: the publisher uses numbered paragraphs
of the chapter-number variety, eg, [12-125], and index entries should
point to the relevant paragraph. Rearranging paragraphs or inserting a
new one made a mess of *everything* when using Word.
My nephew, a mathematician, suggested that I have a look at LaTeX and
helped me get started.
I'm very, very happy with using LaTeX for writing. The usual reasons:
enforced structure, automatic adjustments when rearranging material,
embedded index entries, automatic generation of tables, the ability to
use version control, etc. Maintaining a 700+ page book with a zillion
cross references, index entries, and multiple indexes became a breeze. I
could concentrate on writing.
The only problem has been interaction with editors, and I am now senior
enough to insist that the editor edit my files directly. I'll get
him/her to use TexStudio or something similar to edit my files directly.
This will deal with the last problem: that of introduced errors through
transcribing editor's corrections.
I would abandon the book rather than go back to Word :-).
End of rant.
Alan L Tyree http://www2.austlii.edu.au/~alan
Tel: 04 2748 6206 sip:email@example.com
next prev parent reply other threads:[~2013-09-08 22:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 23:07 Index of cases Alan L Tyree
2013-09-08 2:05 ` David Rogers
2013-09-08 5:56 ` Alan L Tyree
2013-09-08 4:37 ` Jambunathan K
2013-09-08 6:18 ` Alan L Tyree
2013-09-08 7:09 ` Jambunathan K
2013-09-08 7:29 ` Jambunathan K
2013-09-08 22:17 ` David Rogers
2013-09-08 22:55 ` Alan L Tyree [this message]
2013-09-09 6:58 ` David Rogers
2013-09-09 7:14 ` Alan L Tyree
2013-09-09 8:10 ` Suvayu Ali
2013-09-09 19:33 ` Alan L Tyree
2013-09-09 9:41 ` Paul Rudin
2013-09-09 19:41 ` Alan L Tyree
2013-09-09 18:56 ` Achim Gratz
2013-09-10 0:40 ` Brian van den Broek
2013-09-10 4:01 ` Alan Tyree
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).