From: "Peter Münster" <pmlists@free.fr>
Subject: Re: newest version on teTeX-3.0
Date: Tue, 7 Jun 2005 19:25:12 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0506062123040.9379@gaston.free.fr> (raw)
In-Reply-To: <42A3375D.6030003@elvenkind.com>
On Sun, 5 Jun 2005, Taco Hoekwater wrote:
> Barring typo's, this wiki page should be a help for people trying
> to upgrade a 'normal' teTeX:
>
> http://contextgarden.net/TeTeX_3.0_installation
Indeed, a great help! Thank you!
Here the result on my machine:
I've followed all the steps on your page, and then:
This is dvips(k) 5.95a Copyright 2005 Radical Eye Software (www.radicaleye.com)
' TeX output 2005.06.06:1049' -> test.ps
<tex.pro><ec-lm.enc><texps.pro>. <lmr12.pfb>[1]
So dvips seems ok.
texexec --pdf test:
fonts : using map file: original-base
fonts : using map file: ec-public-lm
fonts : using map file: ec-base
fonts : using map file: original-ams-base
fonts : using map file: original-public-lm
systems : begin file test at line 3
[1.1{/opt/teTeX/texmf-dist/fonts/map/dvips/context/original-empty.map}{/opt/teT
eX/texmf-dist/fonts/map/dvips/context/original-base.map}{/opt/teTeX/texmf-dist/
fonts/map/dvips/context/ec-public-lm.map}{/opt/teTeX/texmf-dist/fonts/map/dvips
/context/ec-base.map}{/opt/teTeX/texmf-dist/fonts/map/pdftex/context/original-a
ms-base.map}{/opt/teTeX/texmf-dist/fonts/map/dvips/context/original-public-lm.m
ap}]
systems : end file test at line 5
) </var/tmp/texfonts/pk/modeless/public/lm/ec-lmr12.72pk>
Output written on test.pdf (1 page, 2742 bytes).
Transcript written on test.log.
This is a bitmap font, and very ugly with Acroread...
Then I removed the lines 75-107 (from "\resetmapfiles" to "\fi") from
cont-sys.rme (and saved it as cont-sys.tex). After that, I got a pdf-file
with type 1 fonts, but a lot of warnings like this one:
Warning: pdfetex (file /opt/teTeX/texmf-var/fonts/map/pdftex/updmap/pdftex.map)
: fontmap entry for `bchb8r' already exists, duplicates ignored
So, there are a lot of duplicates in pdftex.map (about 600), like:
vnti8 LMRoman8-Italic "enct5psn ReEncodeFont" <t5psn.enc <lmri8.pfb
vnti8 VNTI8 <vnti8.pfb
What is the right method, to avoid these warnings?
TIA for any hints!
Cheers, Peter
--
http://pmrb.free.fr/contact/
next prev parent reply other threads:[~2005-06-07 17:25 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
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 [this message]
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=Pine.LNX.4.58.0506062123040.9379@gaston.free.fr \
--to=pmlists@free.fr \
--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).