From: Zeljko Vrba <mordor@fly.srk.fer.hr>
Subject: Re: ConTeXt vs. LaTeX
Date: Thu, 5 Aug 2004 08:42:08 +0200 [thread overview]
Message-ID: <20040805064208.GB4580@fly.srk.fer.hr> (raw)
In-Reply-To: <20040804210901.GA28298@muisje>
On Wed, Aug 04, 2004 at 11:09:01PM +0200, Siep Kroonenberg wrote:
>
> The right way to handle this would have been to copy just the
> relevant code fragment to a package or classfile of your own and
> modify it. The code would have looked a lot hackier than
> corresponding Context code, but as long as it sits neatly tucked
> away in a package of its own, you wouldn't have to let that bother
> you.
>
Ah, but I have only simplest experience in TeX programming (simple,
non-recursive \defs and \lets are my greatest achievment) and what you
are suggesting is still out of my reach..
1. I know very little of plain TeX and LaTeX internals to be able to do
anything significant programming for latex.
2. I don't like asking for help. Partly because I don't want to bother
people, partly because I'm impatient waiting for an answer. When I ask
for help, I'm really desperate.
Context has enabled me to do typesetting the way I want without too much
'expert' advice and customization.. I had a few questions on Context a
few years ago when reference manuals were non-existant.. But now I'm able
to do everything I want on my own. Still with virtually no 'real' TeX
programming.
prev parent reply other threads:[~2004-08-05 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 14:07 Mojca Miklavec
2004-08-04 16:58 ` Zeljko Vrba
2004-08-04 21:09 ` Siep Kroonenberg
2004-08-05 6:42 ` Zeljko Vrba [this message]
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=20040805064208.GB4580@fly.srk.fer.hr \
--to=mordor@fly.srk.fer.hr \
--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).