From: Hans Hagen <pragma@wxs.nl>
Subject: Re: newest version on teTeX-3.0
Date: Sat, 04 Jun 2005 12:20:28 +0200 [thread overview]
Message-ID: <42A1806C.1030701@wxs.nl> (raw)
In-Reply-To: <Pine.LNX.4.58.0506032247390.27811@gaston.free.fr>
Peter Münster wrote:
> Hello,
> does somebody already have some experience with the installation of the
> newest ConTeXt version (2005.06.03) on teTeX-3.0 ?
> With a minimal test-file (\starttext hello \stoptext) I have still two
> little problems:
>
> "texexec test" runs ok, but "dvips test" gives the following messages:
>
> This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com)
> ' TeX output 2005.06.03:2232' -> test.ps
> dvips: expected number in \printpaperwidth ,\printpaperheight, returning 10
> dvips: expected units in \printpaperwidth ,\printpaperheight, assuming inches.
> dvips: expected number in \printpaperwidth ,\printpaperheight, returning 10
> dvips: expected units in \printpaperwidth ,\printpaperheight, assuming inches.
> kpathsea: Running mktexpk --mfmode ljfzzz --bdpi 1200 --mag 1+0/1200 --dpi 1200 ec-lmr12
> mktexpk: don't know how to create bitmap font for ec-lmr12.
> kpathsea: Appending font creation commands to missfont.log.
> dvips: Font ec-lmr12 not found, characters will be left blank.
> <tex.pro>. [1]
>
> The problem with the \printpaperwidth etc is not so serious, since I can
> overwrite the \dosetuppaper macro:
> \definespecial\dosetuppaper#1#2#3{%
> \special{papersize=\the\printpaperwidth,\the\printpaperheight}}
safer is:
\definespecial\dosetuppaper#1#2#3%
{\begingroup
\!!dimena#1%
\!!dimenb#3%
\special{papersize=\the\!!dimena,\the\!!dimenb}%
\endgroup]
> But for the ec-lmr12 problem, I would appreciate some help. I've already
> tried some commands like "updmap-sys --enable Map ec-public-lm.map" but
> without success.
i'm not familiar with updmap
(dvipdfm works ok now, is there a mapfile loading special in dvips?)
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:[~2005-06-04 10:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 21:07 Peter Münster
2005-06-04 10:20 ` Hans Hagen [this message]
2005-06-04 8:50 ` John R. Culleton
2005-06-04 14:05 ` Hans Hagen
2005-06-04 19:17 ` Peter Münster
2005-06-04 19:24 ` Taco Hoekwater
2005-06-05 6:14 ` Peter Münster
2005-06-04 21:30 ` Hans Hagen
2005-06-05 6:15 ` Peter Münster
2005-06-05 17:33 ` Taco Hoekwater
2005-06-07 17:25 ` Peter Münster
2005-06-07 17:58 ` Taco Hoekwater
2005-06-07 20:01 ` Peter Münster
2005-06-07 21:42 ` Taco Hoekwater
2005-06-07 21:43 ` Taco Hoekwater
2005-06-08 7:38 ` Hans Hagen
2005-06-08 16:33 ` Tobias Burnus
2005-06-08 20:41 ` Hans Hagen
2005-06-08 16:41 ` Peter Münster
2005-06-07 20:07 ` Patrick Gundlach
2005-06-07 21:31 ` Taco Hoekwater
2005-06-08 7:32 ` Hans Hagen
2005-06-08 7:45 ` Patrick Gundlach
2005-06-08 12:47 ` Hans Hagen
2005-06-08 12:51 ` Patrick Gundlach
2005-06-08 14:16 ` Hans Hagen
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=42A1806C.1030701@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).