ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Re: Installation problem
Date: Tue, 22 Jun 2004 10:32:49 +0200	[thread overview]
Message-ID: <40D7EEB1.60901@wxs.nl> (raw)
In-Reply-To: <m2659kocrq.fsf@levana.de>

Patrick Gundlach wrote:

>               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?
>  
>
maybe some interference with cont-en.ini; does

  texexec --make --alone

work ok?

it should not bark on the cp8bit (btw the latest version should use natural.tcx which is in the context distribution, cp8bit is flawed and not really 8 bit [straight in->out mapping is needed for instance for 
runtime xslt processign and such]; next year we can use -8bit 

(this whole 8 bit mess-up has been hauting me for years -)  


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

  reply	other threads:[~2004-06-22  8:32 UTC|newest]

Thread overview: 21+ 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
2004-06-22  8:32               ` Hans Hagen [this message]
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 17:06   ` David Arnold
2004-10-17 20:06     ` h h extern
2004-10-16 15:46 ` Problem Larry Stamm
2004-10-16 19:08   ` David Arnold

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=40D7EEB1.60901@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).