From: Douglas Philips <dgou@mac.com>
Subject: Re: Manual (English) Update soon?
Date: Fri, 29 Dec 2006 11:14:52 -0500 [thread overview]
Message-ID: <9D262742-4464-4342-8EA8-EA01AAC9A344@mac.com> (raw)
In-Reply-To: <alpine.WNT.0.81.0612281645380.3492@nqvgln>
On 2006 Dec 28, at 5:00 PM, Aditya Mahajan indited:
> On Thu, 28 Dec 2006, Douglas Philips wrote:
>> cont-eni.pdf (ConTeXt the manual by Hans Hagen, November 12th, 2001).
>
> That is the most up to date manual and should get you started for most
> of the basic features. The features that are not in the manual are
> mostly related to specific needs, so you can get around even if you do
> not know about them. Some My Ways discuss some of these undocumented
> features.
The undocumented features are documented in My Ways? :-)
I found a few of those also, and it is very confusing to a newbie
(such as myself) to figure out what is old and valid and what is old
and not-so-valid...
> Just give it a shot. The is "Latex in proper context" by Berend de
> Boer which can help in the transition. The general information on
> http://wiki.contextgarden.net/From_LaTeX_to_ConTeXt is also useful.
Cool, thanks!
> Context is very stable, and much better documented than latex. You can
> start with small documents in context to get comfortable with it. The
> best documents to start are those where you do not have a strict
> formatting requirement, so that you do not need to worry if you can
> not get something working.
:-) That would be ideal. However, I'm looking to change horses
because the documents I am already producing (newsletters for local
groups (all volunteer)) are straining at what LaTeX wants me to do.
So, I've been contemplating whether I should move "up" the
abstraction ladder to ConTeXt or "down"
to plain TeX and really learn to build the world from boxes and
glue. :-)
I'd rather move up. :-) :-)
>> (IIRC, Hans is also a core team member of LuaTeX, so perhaps I should
>> just suck it up with LaTeX until LuaTeX is viable?)
>
> LuaTeX is not a replacement for LaTeX. It is a replacement for pdfTeX.
> ...
> pending feature requests getting implemented. So, if you are planning
> on switching to context, there is no real need to wait for luatex.
OK. Wasn't sure...
> HTH,
> Aditya
Yes, it did/does, thank you!
--Doug
next prev parent reply other threads:[~2006-12-29 16:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 21:10 Douglas Philips
2006-12-28 22:00 ` Aditya Mahajan
2006-12-29 16:14 ` Douglas Philips [this message]
2006-12-30 3:04 ` Mojca Miklavec
2006-12-30 9:28 ` Douglas Philips
2007-01-02 22:28 ` Henning Hraban Ramm
2006-12-30 5:47 ` Sanjoy Mahajan
2006-12-30 9:40 ` Douglas Philips
2006-12-30 11:43 ` Rolf Marvin Bøe Lindgren
2006-12-30 18:38 ` Sanjoy Mahajan
2006-12-30 19:45 ` Rolf Marvin Bøe Lindgren
2006-12-29 0:43 ` Mojca Miklavec
2006-12-29 1:58 ` John R. Culleton
2006-12-29 4:37 ` Idris Samawi Hamid
2006-12-29 16:35 ` Douglas Philips
2006-12-29 19:22 ` andrea valle
2006-12-30 9:20 ` Douglas Philips
2006-12-29 17:38 ` plink
2006-12-30 9:17 ` Douglas Philips
2007-01-01 22:32 ` Hans Hagen
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=9D262742-4464-4342-8EA8-EA01AAC9A344@mac.com \
--to=dgou@mac.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).