From: Hans Hagen <pragma@wxs.nl>
Cc: johannes.huesing@uni-essen.de, ntg-context@ntg.nl
Subject: Re: format file, where?
Date: Sun, 29 Oct 2000 23:28:00 +0100 [thread overview]
Message-ID: <3.0.6.32.20001029232800.01924d70@pop.wxs.nl> (raw)
In-Reply-To: <00102820492701.04659@melfpelts>
At 08:44 PM 10/28/00 +0200, Johannes Hüsing wrote:
>Am Sam, 28 Okt 2000 schrieb Hans Hagen:
>> At 11:01 PM 10/27/00 +0200, Johannes Hüsing wrote:
>[...]
>> >failed though, as fmtutil didn't find cont-{en,de,nl,uk}.fmt. These
>files > >don't seem to be in the tree which was generated after
>unpacking. So where > >do I find those format files?
>>
>> Nowhere yet,
>>
>> either run "texexec --make --alone"
>
>fmtutil: no info for format `cont---alone'
>
>> or run "fmtutil --edit" and uncomment
>> the context lines [will probably be default in a next tetex version].
>>
>
>They were uncommented. As I gather from the fmtutil description,
>fmtutil requests the existance of cont-*.ini somewhere, which I didn't
>find in the path.
../tex/context/config
% Thomas Esser, 1998, 1999. public domain.
\input cont-en.tex
\endinput
>Another question that turned up: In one of my documents, some
>included PNG-formatted graphics were not shown (grey rectangles
>instead.) As this happens to St. Stephanus church in the beginners
>manual as well, I presume a feature of acrobat reader?!
Maybe a bug
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
prev parent reply other threads:[~2000-10-29 22:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 21:01 Johannes Hüsing
2000-10-28 14:26 ` Hans Hagen
2000-10-28 18:44 ` Johannes Hüsing
2000-10-29 22:28 ` Hans Hagen [this message]
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=3.0.6.32.20001029232800.01924d70@pop.wxs.nl \
--to=pragma@wxs.nl \
--cc=johannes.huesing@uni-essen.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).