[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#184875: (fwd) Bug#184875: tetex-bin: dvips -Ppdf won't work at all



Dear Timothey, dear Karl,

Down here in the Debian Bug Tracking System we've got a Bug report
about problems when trying to generate fonts with a very high
resolution. The problem occurs, when I use fonts, which are not
available as PS-Type1-fonts and call dvips with the -Ppdf option.
Example:

\documentclass{minimal}
\usepackage[T1]{fontenc}
\begin{document}
test
\end{document}

The original bug report and a possible analysis follows. As I don't
know, whom I should blame I send the message to you both.

Thanks in advance,
  Hilmar
----- Forwarded message from Hilmar Preusse <hille42@web.de> -----

From: Hilmar Preusse <hille42@web.de>
Reply-To: Hilmar Preusse <hille42@web.de>, 184875@bugs.debian.org
To: "Silas S. Brown" <ssb22@cam.ac.uk>, 184875@bugs.debian.org
Subject: Bug#184875: tetex-bin: dvips -Ppdf won't work at all
Date: Fri, 4 Apr 2003 16:00:20 +0200
Message-ID: <20030404140020.GA29549@preusse-16223.user.cis.dfn.de>
References: <E18u7si-0006kE-00@ssb22.joh.cam.ac.uk>
User-Agent: Mutt/1.3.28i
Organization: Hilmar Preusse Inc.
X-Mailing-List: <debian-tetex-maint@lists.debian.org> archive/latest/4356

On 15.03.03 Silas S. Brown (ssb22@cam.ac.uk) wrote:

Hi,

> Help!  I try "dvips -Ppdf somefile.dvi" and I get lots of
> "font not found" messages from mktexpk, and sure enough
> there are lots of blank characters.  This started happening
> after I re-installed Debian stable from CD onto a fresh
> partition after having too many problems with testing.  I'm
> positive I've got the right font packages installed (I
> haven't changed my package list).
> 
> If I try "xdvi" then that works; if I try "dvips -Ppdf"
> after doing xdvi, it does find most (but not all) of the
> fonts - it scales up the versions that xdvi used (which is
> not so good but better than nothing).  Still loads of
> characters missing in the postscript.
> 
Sorry me again. I'm just reading through some bug reports and I've
got an idea, what could have happened. Some of the fonts you used are
not available as Type1. Hence mktexpk tried to create some from the
mf sources at resolution of 8000 dpi (see
/etc/texmf/dvips/config.pdf).

% Default resolution. Attempt to make `resolution independent'.
% Resolution set to 8000dpi (could be as high as 10000).

D 8000

However there is no mode in /etc/texmf/modes.mf for such a high
resolution, therefore mktexpk bombs out:

drachi:[hille] >dvips -Ppdf a
This is dvips(k) 5.86e Copyright 2001 Radical Eye Software (www.radicaleye.com) ' TeX output 2003.04.04:1521' -> a.ps
kpathsea: Running mktexpk --mfmode ljfour --bdpi 8000 --mag 1+0/8000 --dpi 8000 ecrm1000
mktexpk: Mismatched mode ljfour and resolution 8000; ignoring mode.
mktexpk: Can't guess mode for 8000 dpi devices.
mktexpk: Use a config file, or update me.
kpathsea: Appending font creation commands to missfont.log.
dvips: Font ecrm1000 not found,  using cmr10 instead.
dvips: Checksum mismatch in font ecrm1000
<tex.pro><alt-rule.pro><texc.pro>. [1]

Two solutions:
1. Create a mf-mode with that resolution.
2. Use another mode with a smaller resolution, e.g. 600 dpi, like you
did using -D600. However that will give more worse results.

There will still be Type3-fonts in that file, which will look ugly.
I'll surf a little bit in the web, how this could be solved. It could
have an effect on #132459 too.

H. 
-- 
sigmentation fault

-- 
To UNSUBSCRIBE, email to debian-tetex-maint-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

----- End forwarded message -----

-- 
sigmentation fault



Reply to: