From: CB <cb.lists@gmail.com>
Subject: Re: Context, LaTeX, or an XML for academic writing?
Date: Wed, 11 May 2005 09:52:59 +1000 [thread overview]
Message-ID: <4281495B.5020200@gmail.com> (raw)
In-Reply-To: <427F31EA.6000806@kpatents.com>
Hi Ville,
Thanks for your reply. I don't have much more to say on this yet, but
have added a few comments below.
>
> I was in a similar situation a few years ago (writing my PhD thesis).
> I think you are absolutely right when you avoid Word and everything
> Wordish. Making a big document with Word requires a lot of knowledge
> about what you should avoid. And in the end you'll still spend your
> nights wondering why the **** the crossreferences or page numbers go
> wrong.
Absolutely. Word seems easy at first, but I've watched people go gray
trying to get large texts to do what they want, close to deadline.
>
> However, your wishlist looks a bit difficult.
Actually your comment here might suggest how far we have to go then, as
I'd consider my wishlist a very roughly stated but really quite minimal
set of requirements for academic writing.
>
> The situation becomes much more complicated if you need RTF. It is a
> completely different story, a word processor editable format. I guess
> you don't really want to distribute your work in editable format, and
> PDF can be read with virtually any computer.
>
> I'd say it'll fill number 2, as well. But RTF, no. There may be
> kludges to make it kind of, you know, a bit like, errr, RTFish, but
> nothing really good. The reason is simple: the two things are far
> apart from each other.
Since posting I've thought a bit more about why I wanted RTF, and
realised it wouldn't do what I wanted anyway. The 'inter-operation with
Word users' I was referring to is primarily this: it's common amongst
academics I know here in Australia to use some of the collaboration
features of Word (marginal comments and revision control, particularly).
RTF wouldn't actually help with those anyway. So there's really no way
around this without using Word, which I will only do at gunpoint.
next prev parent reply other threads:[~2005-05-10 23:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 2:58 CB
2005-05-09 9:48 ` Ville Voipio
2005-05-10 23:52 ` CB [this message]
2005-05-11 6:52 ` Henning Hraban Ramm
2005-05-12 13:46 ` Ville Voipio
2005-05-13 0:05 ` CB
2005-05-14 12:45 Tobias Wolf
2005-05-16 17:50 ` John R. Culleton
2005-05-17 0:59 ` Tobias Burnus
2005-05-17 12:41 ` Tobias Wolf
2005-05-17 4:03 ` Matthias Weber
[not found] ` <e06bd0fe050517055047c3210b@mail.gmail.com>
2005-05-17 12:52 ` Tobias Wolf
2005-05-17 22:41 Ville Voipio
2005-05-18 2:10 ` Paul Tremblay
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4281495B.5020200@gmail.com \
--to=cb.lists@gmail.com \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).