ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: context w/ fptex?
Date: Thu, 07 Oct 1999 09:25:20 +0100	[thread overview]
Message-ID: <37FC58F0.EB08CE61@wxs.nl> (raw)
In-Reply-To: <19991006131209.A22999@vasili.rlf.org>

Thomas Porter wrote:

> $IniPath = `$kpsewhich --format="other text files" -progname=context
> texexec.ini` ;
> 
> Evidently, it did not interpolate the $kpsewhich variable, but tried to execute
> "$kpsewhich" directly.  At any rate, I took the '$' off and it ran OK.

Hm. When I look at the code, it looks like texexec cannot find it's ini
file. Did you copy texexec.rme to texexec.ini and checked its content? 

> So then I tried 'perl c:\tex\texmf\context\preltk\texexec.pl --make en' and got
> errors related to paths in texmf.cnf.  Fixed those and finally ran into errors
> with pool sizes.  Tweaked texmf.cnf to look more like my Linux one as far as
> context-related pool, hash, string, etc sizes went, and reran.  Finally got
> errors on memory being exceeded like so:

When set up ok, texexec will pass the appropriate switch
progname=context to pdftex, which will make sure it can identify the
right mem values in texmf.cnf 

> (c:/TEX/texmf/tex/context/base/font-cmr.tex
> Runaway argument?
> {\unexpanded \setvalue {12ptrm
> ! TeX capacity exceeded, sorry [main memory size=263001].
> <argument> ...b}}} {\unexpanded \setvalue {12ptrmb
>                                                   sb}{\doloadfont {12pt}{rm}...
> 
> Anyone else running context with fptex 2.4.2?  Any suggestions for a better
> win32 tex to go with?  Any pointers to how to make context work with miktex, if
> I go back that way?

I will send you the latest, updated fptex make utility (there was a bug
in previous ones) in a separate mail. Untested, but reported ok by
Stazek. 

There is a new installation manual, which explains installing texexec; a
dedicated miktex section will be added in a few days (Walter Kehowski
had a smooth installation). 

> This would be pretty neat to get to work under win98.  I admire the people who
> have worked so hard to get TeX to work under DOS/WIN in spite of all its
> limitations.

(btw, I run fptex binaries, not the whole system, in a somewhat unusual
texmf tree)

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.nl
-----------------------------------------------------------------


  reply	other threads:[~1999-10-07  8:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-06 17:12 Thomas Porter
1999-10-07  8:25 ` Hans Hagen [this message]
1999-10-07 14:27   ` Thomas Porter

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=37FC58F0.EB08CE61@wxs.nl \
    --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).