ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: siepo@client44-3.kabelA.oprit.rug.nl
Subject: Re: beginner's questions
Date: Sat, 11 Nov 2000 18:34:17 +0100 (CET)	[thread overview]
Message-ID: <20001111173713.26A132317E@client44-3.kabela.oprit.rug.nl> (raw)
In-Reply-To: <m3r94laqx9.fsf@coe.uga.edu>

On  9 Nov, Ed L Cashin wrote:
> Hans Hagen <pragma@wxs.nl> writes:
> 
>> >- Most of the work I plan to make with context are small (<20pages)
>> >  reports. Mostly text with some tables and pictures, and a few
>> >  graphs. Is context the program to handle this, or should I choose
>> >  latex? After a quick look at the docs, it seems context is easier
>> >  to do most things. Is this correct?
>> 
>> that's for others to answer -) 
> 
> The possible conditions for choosing LaTeX over ConTeXt that come to
> mind are these:
> 
>   * if your publisher requires it
> 
>   * if you must collaborate with latex users on a document
> 
>   * if you do no unusual documents, only math papers and physics
>     papers (then you won't notice the incompatibilities and
>     limitations as much)
> 
> ... but then again, there are a lot of LaTeX features that I don't
> use, since I only produce English-language documents, so I don't know
> about much of the LaTeX world.  But from what I've heard here, ConTeXt
> is happy being multi-lingual, and I wouldn't guess that LaTeX has an
> advantage.
> 
> But using ConTeXt is much more fun.  When I ask, "can I do this?" the
> answer is "Yes."  With LaTeX the answer was often, "No."

A dissenting voice: I don't think Context is easier than LaTeX. One
stumbling block is the documentation - there is a lot of it, but I find
it hard to find my way around in it - another is the sheer mass of
Context, which makes it hard to find things and to debug problems.
Debugging is hampered even more by the multilingual interface and by all
the internal space-eating dummy parameters.

In practice, I need to write just as much plain TeX with Context as with
LaTeX, and I need to ask a lot more questions in order to get the job
done. And in Context I encounter just as many mysterious goings-on as in
LaTeX.

I use Context when I have to, but in general I much prefer LaTeX.

Two things in favour of Context: other than LaTeX, it is capable of
producing a tight column layout. Also, Hans is very responsive and
helpful when you have a problem.

-- 
Siep Kroonenberg


  reply	other threads:[~2000-11-11 17:34 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-09 16:51 Wouter Verheijen
2000-11-09 17:20 ` Frans Goddijn
2000-11-09 17:54   ` Hans Hagen
2000-11-09 17:40 ` Hans Hagen
2000-11-09 19:25   ` Ed L Cashin
2000-11-11 17:34     ` siepo [this message]
2000-11-11 17:56       ` Frans Goddijn
2000-11-24 12:51         ` Christopher Tipper
2000-11-11 19:41       ` Berend de Boer
2000-11-12 11:34         ` siepo
2000-11-12 18:56           ` Denis B. Roegel
2000-11-13  9:37             ` Hans Hagen
2000-11-13 16:54               ` multi-column spread control (was Re: beginner's questions) Ed L Cashin
2000-11-13 17:17                 ` Hans Hagen
2000-11-13 18:43                   ` Ed L Cashin
2000-11-13 18:44                   ` Ed L Cashin
2000-11-14  7:49                     ` Hans Hagen
2000-11-14 13:27                       ` Ed L Cashin
2000-11-14 14:13                         ` Hans Hagen
2000-11-14 14:49                           ` Ed L Cashin
2000-11-14 15:49                             ` Hans Hagen
2000-11-14 16:45                               ` Ed L Cashin
2000-11-14 17:12                                 ` Hans Hagen
2000-11-14 18:25                                   ` Ed L Cashin
2000-11-15  0:23                                     ` Hans Hagen
2000-11-15  1:15                                       ` Ed L Cashin
2000-11-15 17:20                                         ` voting & form design (was: multi-column spread control) Hraban
2000-11-14 21:51                                   ` multi-column spread control (was Re: beginner's questions) Denis B. Roegel
2000-11-15  0:20                                     ` Hans Hagen
2000-11-15 23:28                                       ` Denis B. Roegel
2000-11-19 19:31                                         ` Hans Hagen
2000-11-12 14:04         ` Documentation Tasks (was: " Hraban
2000-11-13  7:38       ` beginner's questions Hans Hagen
2000-11-13 21:26         ` siepo
2000-11-09 19:19 ` Berend de Boer
  -- strict thread matches above, loose matches on Subject: below --
2002-09-27 21:14 Michael Na Li
2002-09-28  9:07 ` Michael Na Li
2002-09-28  9:35 ` Jens-Uwe Morawski
2002-09-29  6:38   ` Michael Na Li
2002-09-29 16:35 ` Henning Hraban Ramm
2002-09-30  8:11 ` Taco Hoekwater
     [not found] <Hans Hagen's message of "Tue, 14 Nov 2000 18:12:11 +0100">
     [not found] ` <Hans Hagen's message of "Tue, 14 Nov 2000 16:49:12 +0100">
     [not found]   ` <Hans Hagen's message of "Tue, 14 Nov 2000 15:13:29 +0100">
     [not found]     ` <Hans Hagen's message of "Tue, 14 Nov 2000 08:49:03 +0100">

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=20001111173713.26A132317E@client44-3.kabela.oprit.rug.nl \
    --to=siepo@client44-3.kabela.oprit.rug.nl \
    --cc=siepo@cybercomm.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).