From: Idris Samawi Hamid <ishamid@colostate.edu>
Subject: Re: compile problems
Date: Sun, 27 Jun 2004 11:43:36 -0600 [thread overview]
Message-ID: <opr99kuyjbu9mfh0@lamar.colostate.edu> (raw)
In-Reply-To: <opr97tr5bxu9mfh0@lamar.colostate.edu>
Hi,
There is really something screwy going on with the latest beta; what is
the problem calling upon the /texmf/web2c/natural.tcx file?? I hope
someone can help with this soon; this is like having a flat tire in the
middles of nowhere...
On Sat, 26 Jun 2004 13:01:07 -0600, Idris Samawi Hamid
<ishamid@colostate.edu> wrote:
> Hi gang,
>
> I'm having trouble compiling the eomega format with the latest ConTeXt
> (6-21):
>
> \texmf-var\web2c>eomega --ini *plain \dump
>
> works, but then
>
> \texmf-var\web2c>texexec --make --alone en -tex=eomega
> eomega: unrecognized option `-translate-file=natural.tcx'
> Try `eomega --help' for more information.
>
> fails. On the other hand
>
> eomega --ini *cont-en
>
> works, but then I get e.g.,
>
> executable : EOMEGA
> format : cont-en
> inputfile : decision
> output : standard
> interface : en
> current mode : none
> TeX run : 1
>
> EOMEGA: unrecognized option `-translate-file=natural.tcx'
> Try `EOMEGA --help' for more information.
>
> Please help!
>
> Best
> Idris
--
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next prev parent reply other threads:[~2004-06-27 17:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 19:01 Idris Samawi Hamid
2004-06-27 7:51 ` Giuseppe Bilotta
2004-06-27 17:43 ` Idris Samawi Hamid [this message]
2004-06-27 17:55 ` Re[2]: " Giuseppe Bilotta
2004-06-27 18:21 ` Idris Samawi Hamid
2004-06-27 18:27 ` Idris Samawi Hamid
2004-06-27 18:37 ` Patrick Gundlach
2004-06-27 18:39 ` Re[2]: " Idris Samawi Hamid
2004-06-27 18:51 ` Patrick Gundlach
2004-06-27 19:00 ` Idris Samawi Hamid
2004-06-28 8:08 ` Hans Hagen
2004-06-28 9:07 ` Re[2]: " Giuseppe Bilotta
2004-06-28 13:05 ` Olaf Weber
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=opr99kuyjbu9mfh0@lamar.colostate.edu \
--to=ishamid@colostate.edu \
--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).