From: "Manuel P." <ayeye.sysforge@gmail.com>
To: context-ml <ntg-context@ntg.nl>
Subject: Thoughts on ConTeXt: ditched
Date: Sun, 27 Dec 2009 16:54:47 +0100 [thread overview]
Message-ID: <4B378347.8020700@gmail.com> (raw)
ConTeXt is a good software. I was impressed with a manual typesetted
with it and decided to give it a try. After some small documents,
despite my ridicously small knowledge of it I decided to use ConTeXt for
my thesis. Bad move.
ConTeXt is beautiful because it's very configurable, for the most uses
doesn't need any external module (unlike LaTeX), and gives me more power
on the presentation of the document. But in a few days of work I've come
to realize that it's not suited for me and this project.
I've had some unpleasant surprises:
- Bibliography doesn't work the way it should on MKIV. Unlike MKII.
- MKIV, unlike MKII, doesn't setup any background color:
----
\setupcolors[state=start]
\setupbackground[background=screen]
\setupbackground[state=start]
\def\quotebox#1#2
{\blank
\midaligned{\startbackground
\quotation{\em #1} \crlf --#2
\stopbackground}
\blank}
----
- the above \quotebox command, in some cases, sends pdftex and luatex
(MKII and MKIV) to the moon with an infinite loop (100% CPU).
One reason for this is probably my very limited knowledge and experience
with ConTeXt. It's extremely configurable, and this is a plus. But on
the other hand if you don't know how to move, what to do, the system
internals and how any configuration affect the typesetting, a lot of
thing won't work. And worse, you won't know where to bump your head. I
don't have time to read the reference manual (I've already read the
excursion) because the deadline is too near, so I have to call defeat
and go to the LaTeX camp. I've wasted days of work, now I can't afford
more of that.
It's a learning experience: don't use an "experimental" (new for me)
tool for an important job. Stick to the tried&tested ones, and use new
stuff only in a safe context (without a near hard deadline).
Maybe, in some future, I'll take again ConTeXt and try to learn it the
proper way. But for now, it's "fired".
For your patience, time and help: thanks to all of you!
A little wish: I hope that when I'll return here there'll be good
documentation (user-oriented) and a single (througly tested, see TDD/BDD
approaches) reference implementation.
--
Manuel P.
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2009-12-27 15:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-27 15:54 Manuel P. [this message]
2009-12-27 18:41 ` Wolfgang Schuster
2009-12-28 13:44 ` Manuel P.
2009-12-28 15:12 ` Khaled Hosny
2009-12-28 17:59 ` Hans Hagen
2009-12-29 12:48 ` Manuel P.
2009-12-29 2:48 ` berend
2009-12-29 12:57 ` Manuel P.
2010-01-03 18:45 ` Piotr Kopszak
2010-01-04 21:46 ` Manuel P.
2009-12-27 19:16 ` Peter Münster
2009-12-27 21:11 ` Hans Hagen
2009-12-28 13:48 ` Manuel P.
2009-12-28 17:19 ` Peter Münster
2009-12-28 11:30 ` Gour
2009-12-28 12:36 ` R. Bastian
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=4B378347.8020700@gmail.com \
--to=ayeye.sysforge@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).