ishamid wrote:

Hi


===== Original Message From mailing list for ConTeXt users

<[EMAIL PROTECTED]>


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.



I'm sure of course that you replaced `eomega' with `aleph';-)

There should be no need to add aleph.exe to your path if you just refresh the fndb, which I'm sure u did also;-)) (I don't know about MacOSX but TeXLive contains a shortcut to that command in Programs=>TeXLive=>Maintanence).

I (or Hans) will send you the stuff Hans sent me if all else fails: that will work for sure.


the latest release contains a texexec:

texexec --make --all --alone --tex=aleph

you can configure texexec.ini to use the engine subpath which is handy when you run pdfetex along side (the new binaries all have the same suffix now; tetex will not support the tds engine subpath, i dunny yet about fptex and miktex; let's hope that they do)

(--engine is also possible in texexec 5.0)

Hans

-----------------------------------------------------------------
                                         Hans Hagen | PRAGMA ADE
             Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                            | www.pragma-pod.nl
-----------------------------------------------------------------

_______________________________________________
ntg-context mailing list
[EMAIL PROTECTED]
http://www.ntg.nl/mailman/listinfo/ntg-context

Reply via email to