From: Hans Hagen <pragma@wxs.nl>
Cc: Giuseppe Bilotta <gip.bilotta@iol.it>, ntg-context@ntg.nl
Subject: Re: [NTG-context] Gamma support in TeXExec?
Date: Tue, 22 Oct 2002 10:24:49 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20021022101312.02d88548@server-1> (raw)
In-Reply-To: <87of9n8p89.fsf@infovore.xs4all.nl>
At 11:19 PM 10/21/2002 +0200, Olaf Weber wrote:
>Hans Hagen writes:
> > At 08:40 PM 10/20/2002 +0200, Olaf Weber wrote:
> >> Hans Hagen writes:
>
> >>> 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;
>
> >> This is an interesting idea, and one I'd be willing to impose on Omega.
>
> > Thanks! It would help a lot.
>
>Still, for my peace of mind I'd like to know a bit more of the
>background, and why getting Omega to use a different suffix will help
>so much. (And does this mean that pdftex and pdfetex should be
>modified as well?)
it would make sense to give pdftex/pdfetex other extensions as well, just
for the sake of consistency
on the other hand, a user can generate a cont-en.efmt file with pdfetex
which is compatible with cont-en.efmt by etex apart from the pdf support,
simply because pdftex is an extension [in the same way, etex is compatible
and could have the same suffix, unless in non compatible ** mode]
omega is different and not compatible (and not that stable either), and so
users would like to use their macro packages (+formats) for both systems,
so having an cont-en.efmt for pdfetex alongside cont-en.oft for omega is a
good solution or that, in that case
texexec --program=omega yourfile
would launch omega and omega would look for the oft file itself (users
nowadays are not that aware of formats and asking them to generate them ...)
so, to be perfect it should be:
tex -> fmt
etec -> efmt (already)
pdftex -> pft
pdfetex -> epmt
omega -> oft
eomega -> eoft
nts -> nfmt (already)
but since pdftex is compatible is less urgent
an alternative is:
web2c/pdftex/pdftex.fmt
web2c/pdftex/pdfetex.fmt
etc
Sorry for the mess, but solutions like pdflatex versus latex versus tex
makes users think that they are all different tex's while it's the same
program with different macros, and pdflatex/latex is actually the same
thing apart from the backend. For context, i would prefer to keep cont-en
as the one and only name for the english interface version, independent of
the texprogram used
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-22 8:24 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 ` [NTG-context] " Hans Hagen
2002-10-20 18:40 ` 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 [this message]
2002-10-22 9:33 ` 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.20021022101312.02d88548@server-1 \
--to=pragma@wxs.nl \
--cc=gip.bilotta@iol.it \
--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).