From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/5383 Path: main.gmane.org!not-for-mail From: Giuseppe Bilotta Newsgroups: gmane.comp.tex.context Subject: Re[2]: New Beta Date: Fri, 24 Aug 2001 16:14:00 +0200 Sender: owner-ntg-context@let.uu.nl Message-ID: <853362420.20010824161400@bigfoot.com> References: <3.0.5.32.20010820180241.0085fa50@mail.northcoast.com> <3B8610DD.45280BAA@ukrpost.net> Reply-To: Giuseppe Bilotta NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1035395975 1229 80.91.224.250 (23 Oct 2002 17:59:35 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Wed, 23 Oct 2002 17:59:35 +0000 (UTC) Cc: ntg-context@ntg.nl Original-To: Olya Briginets In-Reply-To: <3B8610DD.45280BAA@ukrpost.net> Xref: main.gmane.org gmane.comp.tex.context:5383 X-Report-Spam: http://spam.gmane.org/gmane.comp.tex.context:5383 OB> I have found that this is not texexec but solely MiKTeX problem, the problem OB> is that it seems that MiKTeX accept only restricted lenght of its arguments and OB> cuts off the rest of argument for each of arguments separately, so if your OB> TeXFormatPath contains f:/LocalTeXMF/miktex/fmt, then command line argument OB> --undump=f:/LocalTeXMF/miktex/fmt/cont-en are cut after /miktex, so TeX think OB> you wish to use miktex.efmt, not cont-en.efmt. Once you changed --undump= to &, OB> command line are shorter and ain't cut off. I don't know whether it's fixed in OB> MiKTeX 2.1. Is it necessary to use TeXFormatPath? I let MiKTeX find the corred path (or rather put the format files in the default path ...)