From: "Patrick Gundlach" <pg@levana.de>
Subject: Re: Installation problem
Date: 21 Jun 2004 22:51:36 +0200 [thread overview]
Message-ID: <m2659kocrq.fsf@levana.de> (raw)
In-Reply-To: <40D6FAB0.4070504@wxs.nl> (Hans Hagen's message of "Mon, 21 Jun 2004 17:11:44 +0200")
Hello Hans,
>>Using an old texexec works fine for me. I didn't look into this yet.
>>
> hm, maybe some bug due to changed as a result of the new tds and
> binaries; i'll upload my local latest -)
No change.
texexec is /opt/context/2004.6.21/bin/texexec
test$ texexec test
TeXExec 4.3 - ConTeXt / PRAGMA ADE 1997-2004
executable : pdfetex
format : cont-en
inputfile : test
output : standard
interface : en
current mode : none
TeX run : 1
warning: Could not open char translation file `cp8bit.tcx'.
This is pdfeTeX, Version 3.141592-1.11a-2.1 (Web2C 7.5.2)
kpathsea: Running mktexfmt cont-en.efmt
This is pdfeTeXk, Version 3.141592-1.11a-2.1 (Web2C 7.5.2)
\write18 enabled.
%&-line parsing enabled.
(/opt/texlive/8/texmf/web2c/cp8bit.tcx)
**
! End of file on the terminal... why?
running `pdfetex -ini -jobname=cont-en -progname=context *cont-en.ini' ...
This is pdfeTeXk, Version 3.141592-1.11a-2.1 (Web2C 7.5.2) (INITEX)
\write18 enabled.
%&-line parsing enabled.
(/opt/texlive/8/texmf/web2c/cp8bit.tcx)
entering extended mode
(/opt/context/2004.6.21/texmf/tex/context/config/cont-en.ini{/opt/local/texmf/p
dftex/config/pdftex.cfg}
...
cp8bit is not found in the first line, but ok in the 7th.
Do you have an idea what is going on?
Patrick
next prev parent reply other threads:[~2004-06-21 20:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 8:28 Matt Gushee
2004-06-21 8:45 ` Patrick Gundlach
2004-06-21 9:22 ` Matt Gushee
2004-06-21 9:29 ` Patrick Gundlach
2004-06-21 10:06 ` Matt Gushee
2004-06-21 14:57 ` Patrick Gundlach
2004-06-21 15:11 ` Hans Hagen
2004-06-21 20:51 ` Patrick Gundlach [this message]
2004-06-22 8:32 ` Hans Hagen
2004-06-22 8:51 ` Patrick Gundlach
2004-06-22 9:11 ` Hans Hagen
2004-06-22 10:21 ` Patrick Gundlach
2004-06-22 10:35 ` Hans Hagen
2004-06-21 15:34 ` Matt Gushee
2004-06-25 8:32 ` Patrick Gundlach
2004-06-21 8:46 ` Thomas A. Schmitz
2004-06-21 9:05 ` Hans Hagen
2004-10-16 5:43 Installation Problem David Arnold
2004-10-16 9:55 ` Patrick Gundlach
2004-10-16 15:46 ` Problem Larry Stamm
2004-10-17 20:09 ` Installation Problem h h extern
2004-10-17 20:21 ` h h extern
2006-04-08 2:12 Installation problem Pavel Stupin
2006-04-08 3:11 ` Mojca Miklavec
2006-04-08 11:50 ` Hans Hagen
2006-05-03 11:31 installation problem Karsten Heymann
2006-05-05 7:49 ` Taco Hoekwater
2006-05-05 8:02 ` Karsten Heymann
2006-05-05 10:49 ` Hans Hagen
2006-05-23 23:51 Installation Problem Neal Lester
2006-05-24 7:49 ` Taco Hoekwater
2006-05-24 13:45 ` Neal Lester
2006-05-24 16:07 ` gnwiii
[not found] ` <22af238a0605240907w2cf73504h3299e1bf6392de2c@mail.gmail.co m>
2006-05-24 21:36 ` Neal Lester
2006-05-25 12:20 ` gnwiii
2006-05-24 8:13 ` Hans Hagen
2006-05-25 14:48 Neal Lester
2006-05-25 15:15 ` Taco Hoekwater
2006-05-25 15:48 ` Neal Lester
2006-05-25 16:52 ` gnwiii
[not found] ` <22af238a0605250952y9a994fbnab1b342cfed31f06@mail.gmail.com >
2006-05-25 18:39 ` Neal Lester
2006-05-26 10:50 ` gnwiii
2006-05-25 18:41 ` Neal Lester
2006-05-25 16:51 ` gnwiii
2006-05-25 16:58 ` gnwiii
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=m2659kocrq.fsf@levana.de \
--to=pg@levana.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).