From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: [NTG-context] Gamma support in TeXExec?
Date: Sun, 20 Oct 2002 18:48:31 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20021020184536.00afa6e0@remote-1> (raw)
In-Reply-To: <18318954254.20021019181320@iol.it>
At 06:13 PM 10/19/2002 +0200, Giuseppe Bilotta wrote:
>Hello,
>
>I noticed that TeXExec has no "native" support for Gamma, in the
>sense that it doesn't change the "cont-" prefix to "gamma-" when
>the TeX executable is set to Omega.
>
>I did a patch to make this possible, but of course since there are
>no gamma-<language>.tex files, it doesn't work that simply. I
>therefore did a more extensive patch (it has to dump the format as
>cont-en and then rename it) but this is sub-optimal. It would be
>very easy to do if (recent) fpTeX and teTeX supported the
>--job-name option ... is this the case? If so, the patch can be
>done very easily. Anybody using fpTeX or teTeX know about this?
--tex=binary --format=formatname
personally i think that gamma should just use a cont-* file, but with an
ofmt extension; where etex can be distinguished by suffix, omega cannot,
which is a bad thing since now one gets format clashes; i didn't experiment
with this, but it may be possible to set the texformat paths in texmf.cnf
on a per progrma basis (omega.texformats => .../web2c/omega)
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
_______________________________________________
ntg-context mailing list
ntg-context@ref.ntg.nl
http://ref.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2002-10-20 16:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 16:13 Giuseppe Bilotta
2002-10-19 16:23 ` Patrick Gundlach
2002-10-19 16:40 ` Re[2]: " Giuseppe Bilotta
2002-10-19 16:46 ` Re[3]: " Giuseppe Bilotta
2002-10-24 16:46 ` Re[3]: " Olaf Weber
2002-10-25 6:53 ` Re[5]: " Giuseppe Bilotta
2002-10-25 17:54 ` Olaf Weber
2002-10-26 7:10 ` Re[7]: " Giuseppe Bilotta
2002-10-20 16:48 ` Hans Hagen [this message]
2002-10-20 18:40 ` [NTG-context] " Olaf Weber
2002-10-21 6:52 ` Hans Hagen
2002-10-21 21:19 ` Olaf Weber
2002-10-21 21:31 ` Re[2]: " Giuseppe Bilotta
2002-10-22 8:24 ` Hans Hagen
2002-10-22 9:33 ` Re[2]: " Giuseppe Bilotta
2002-10-24 16:48 ` Re[2]: " Olaf Weber
2002-10-25 6:54 ` Re[4]: " Giuseppe Bilotta
2002-10-25 9:00 ` Hans Hagen
2002-10-25 17:59 ` Olaf Weber
2002-10-26 7:13 ` Re[6]: " Giuseppe Bilotta
2002-10-25 9:04 ` Re[2]: " 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=5.1.0.14.1.20021020184536.00afa6e0@remote-1 \
--to=pragma@wxs.nl \
--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).