From: Hans Hagen <pragma@wxs.nl>
Subject: Re: format generation -- again!
Date: Fri, 26 May 2006 23:12:37 +0200 [thread overview]
Message-ID: <44776F45.7010502@wxs.nl> (raw)
In-Reply-To: <28AA4B63-D007-4133-9212-1E58A3A14DB5@uni-bonn.de>
Thomas A. Schmitz wrote:
> Alan's log:
> This is pdfeTeX, Version 3.141592-1.30.4-2.2 (Web2C 7.5.5) (INITEX)
> 24 MAY 2006 06:40
> entering extended mode
> ***cont-en.ini
> (/usr/local/teTeX/share/texmf.local/tex/context/config/cont-en.ini
> (/usr/local/teTeX/share/texmf.local/tex/context/base/cont-en.tex
> (/usr/local/teTeX/share/texmf.local/tex/context/base/context.tex
> (/usr/local/teTeX/share/texmf.local/tex/context/base/syst-pln.tex
>
> Both have the latest release. So the only difference that really
> could matter:
> 1. older version of pdf(e)tex;
>
no problem here
> 2. natural.tcx is not called.
>
probably the problem
> Can anybody help? I'm unable to reproduce the problem here; I can
> generate formats both with texmfstart texexec --make --all and with
> fmtutil-sys --byfmt cont-en.
>
i dunno how fmtutil works, but maybe you can pass the -8bit switch to pdftex somehow (or translate-file=natural.tcx)
an alternative is to regenerate the patterns
ctxtools --pat
will generate them, given that in the meantime the original names/content of pattern sources hasn't changed)
i know from discussion on the tex live list that tetex was ot that fond of being 8 bit clean (all this locale stuff and wanting to have ^^X kind dof output on the terminal) but because context (sometimes) need a round trip 8 bit, i assume an 8 bit clean tex
(btw, fmtutil does not support the engine subpath either - which was reported to be too complex to implement)
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
-----------------------------------------------------------------
next prev parent reply other threads:[~2006-05-26 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 20:18 Thomas A. Schmitz
2006-05-26 21:12 ` Hans Hagen [this message]
[not found] ` <9C5D181C-7C55-4340-8B36-B825A67D6228@princeton.edu>
[not found] ` <C6526E25-59F3-4B6C-9A6D-E70FAE781694@uni-bonn.de>
[not found] ` <CC491E45-EA00-40F3-BF21-859FBCEA20BB@Princeton.EDU>
[not found] ` <61244F54-07BA-4E1A-8EA8-B33F57EF7E69@uni-bonn.de>
[not found] ` <B85021EE-086D-4045-98A3-B7C204E306D7@Princeton.EDU>
[not found] ` <1149022936.4452.1.camel@g5.localnetwork>
[not found] ` <4E0CE6B2-0627-4831-91C2-3E9353211613@Princeton.EDU>
[not found] ` <1149085529.25692.22.camel@g5.localnetwork>
2006-06-01 20:23 ` Alan Bowen
2006-06-01 21:12 ` Hans Hagen
2006-06-01 21:39 ` Alan Bowen
2006-06-01 22:11 ` Hans Hagen
2006-06-02 11:27 ` Alan Bowen
2006-06-02 20:40 ` Alan Bowen
2006-06-02 20:45 ` Aditya Mahajan
2006-06-02 21:00 ` Alan Bowen
2006-06-02 22:21 ` Alan Bowen
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=44776F45.7010502@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).