ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
Subject: Re: ConTeXt and Aleph
Date: Thu, 16 Sep 2004 14:49:54 +0200	[thread overview]
Message-ID: <a06002000bd6f3684d7f9@[62.134.76.187]> (raw)

Hi,

in order to use Aleph in ConTeXt I switched from MacOSX to WinXP.

I installed fptex from the latest TeXLive CD (Sept.2003)
installed the recent ConTeXt beta in my local tree,
installed also the latest (?) Aleph version from CTAN ("bin-aleph-1.15--2.2--RC2-win32-static.zip")
in the main tree and followed the steps Hans once wrote here:


> texexec --make --alone --tex=aleph
> 
> texexec yourfile --tex=aleph --output=dpx
> 
> (or first line of file: % tex=aleph output=dvipdfmx)
> 
> 
> Hans


The result was not working:
***

 TeXExec 4.0 - ConTeXt / PRAGMA ADE 1997-2003



            executable : aleph

                format : cont-en

             inputfile : alephtest1

                output : dvipdfmx

             interface : en

          current mode : none

               TeX run : 1



Der Befehl "aleph" ist entweder falsch geschrieben oder konnte nicht gefunden werden. 
[the command "aleph" is either misspelled or could not be found]

Der Befehl "cont-en" ist entweder falsch geschrieben oder konnte nicht gefunden werden. 
[the command "cont-en" is either misspelled or could not be found]



           return code : 256

              run time : 0 seconds



        total run time : 0 seconds


***


Then I tried the steps Idris recommend once:

> eomega --ini *plain \dump
> eomega --ini *cont-en
> texexec --make en -tex=eomega
> 
> are the relevant commands. eomega _is_ aleph.
> 
> ...
> 
> Idris


The result was the same error output as above.


Could someone who has Aleph successfully running tell me his/her secret, please?

Thank you,
Steffen

             reply	other threads:[~2004-09-16 12:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 12:49 Steffen Wolfrum [this message]
     [not found] ` <a06002000bd6f3684d7f9@[62\.134\.76\.187]>
2004-09-16 14:04   ` Giuseppe Bilotta
  -- strict thread matches above, loose matches on Subject: below --
2004-09-26 15:51 Steffen Wolfrum
2004-09-19 22:17 Steffen Wolfrum
2004-09-17  8:26 Steffen Wolfrum
2004-09-16 18:13 Steffen Wolfrum
2004-09-16 18:12 Steffen Wolfrum
2004-08-17 16:08 Steffen Wolfrum
2004-08-17 16:24 ` Idris Samawi Hamid
2004-08-18  0:15   ` Bob Kerstetter
2004-08-18  3:59     ` Bob Kerstetter
2004-08-18  4:07       ` Steve Peter
2004-08-17 15:26 Steffen Wolfrum
2004-08-17 15:50 ` Hans Hagen
2004-08-17 16:14   ` Idris Samawi Hamid

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='a06002000bd6f3684d7f9@[62.134.76.187]' \
    --to=context@st.estfiles.de \
    --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).