ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Paul Tremblay <phthenry@iglou.com>
Subject: Re: Context, LaTeX, or an XML for academic writing?
Date: Tue, 17 May 2005 22:10:47 -0400	[thread overview]
Message-ID: <20050518021046.GB1123@localhost.localdomain> (raw)
In-Reply-To: <98D0564335EC4848A87BEDEFF4EA056B55C6@posti.kpatents.com>

On Wed, May 18, 2005 at 01:41:00AM +0300, Ville Voipio wrote:
> 
> 
> One of the mixed blessings (=curses) brought about by computers 
> is that now you need to be an academic writer, a typesetter, and
> a graphic artist at the same time. At this point the number
> of should-knows explodes.
> 

[snip]
> ---
> 
> What I am trying to say is that choosing the tool is only
> one part of the project. Whichever tool you choose, you'll 
> end up in trouble at some point. With some tools (WYSIWYG) 
> you'll end up in worse trouble, but even with *TeX the road 
> is bumpy at best, unless you really have a tested and proven 
> templates which you can use.
> 

Yes, this is exactly the problem. I am laying out my girlfriend's
thesis in historic preservation, and it is taking me forever. What a
waste of time! 

The thesis is actually written in  XML. Or rather, she has written it
in MS Word, which I have converted to XML using a very sophisticated
script (http://rtf2xml.sourceforge.net/). I then convert the file to
ConTexT, and then to PDF. There are a million stupid details, like
making sure the title on the cover page is exactly 3 inches from the
top and so fourth. 

This is a waste of time. Why should we be forced to layout pages when
we don't want to? 

Therefore I think a good argument can be made for universities
eventually accepting a thesis in XML format. If they want to be so
picky about layout, they should do it; the student should only be
required to submit the basic information in a structured form.

The assumption of the University is that everyone uses Word. This is a
bad assumption.

Paul

-- 

************************
*Paul Tremblay         *
*phthenry@iglou.com    *
************************

  reply	other threads:[~2005-05-18  2:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-17 22:41 Ville Voipio
2005-05-18  2:10 ` Paul Tremblay [this message]
  -- strict thread matches above, loose matches on Subject: below --
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-07  2:58 CB
2005-05-09  9:48 ` Ville Voipio
2005-05-10 23:52   ` CB
2005-05-11  6:52     ` Henning Hraban Ramm
2005-05-12 13:46     ` Ville Voipio
2005-05-13  0:05       ` CB

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=20050518021046.GB1123@localhost.localdomain \
    --to=phthenry@iglou.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).