From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Re: Announcement: texutil.c
Date: Fri, 19 Mar 2004 09:14:11 +0100 [thread overview]
Message-ID: <20040319091411.5abf302c@glenlivet.elvenkind.com> (raw)
In-Reply-To: <m2vfl26tda.fsf@levana.de>
On 18 Mar 2004 16:57:05 +0100, Patrick wrote:
>
> may I ask you a question: why did you port it to c?
>
For a larger project with ConTeXt that should not depend on the availability
of perl. We needed a very large section of Texutil (--ref and --figures), so it
made sense to port the entire program to C.
Essentially, we will have TeX and Texutil and bits of Texexec in a single
executable, completely without disk-based versions of the tui and tuo file.
I'll probably end up converting some other scripts as well (texfont e.g.)
--
groeten,
Taco
next prev parent reply other threads:[~2004-03-19 8:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 14:10 Taco Hoekwater
2004-03-18 15:57 ` Patrick Gundlach
2004-03-19 8:14 ` Taco Hoekwater [this message]
2004-03-19 9:18 ` Uwe Koloska
2004-03-19 9:36 ` Hans Hagen
2004-03-19 12:56 ` Uwe Koloska
2004-03-19 13:32 ` Hans Hagen
2004-03-19 14:31 ` Tobias Burnus
2004-03-19 13:03 ` Uwe Koloska
2004-03-19 13:34 ` Hans Hagen
2004-03-19 12:31 ` Taco Hoekwater
2004-03-19 12:57 ` Uwe Koloska
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=20040319091411.5abf302c@glenlivet.elvenkind.com \
--to=taco@elvenkind.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).