Bug#132988: Bug fixed
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de>
Subject: Bug#132988: Bug fixed
Date: 07 Mar 2002 16:21:00 +0100
> > Essentially, glpk package should not try to generate
> > PS files in its build process. They will depend highly
> > on system where it is built.
>
> Could you elaborate on that? What exactly would depend on the system,
> and what part of the system? And why is this different from dvi?
Its errors said
Prescanning .kpathsea: Running mktexpk --mfmode canonex --bdpi 600 --mag 1+437/600 --dpi 1037 cmbx12
but if one who sets up system with dpi=400 builds the package
then generated PKs are different and so generated PS files
are different from the original package.
But DVI uses only TFM files so it does not depend on system
settings like DPI etc.
> > If documents are really necessary then it is much
> > better to do "make dvi" instead of "make ps", IMHO.
>
> This would it make much harder for many people to print it.
>
> > In this sence, this should be essentially a bug of glpk.
> > Please contact us before reassigning a bug to teTeX.
>
> Hmm, I don't quite understand. Are you implying all packages that
> build PS documentation are buggy?
In case a PS file is generated from a DVI file, it is not
good at least.
If it is really necessary to provide PS files generated
from DVI then it will be better to generate PS files with
Type1/bluesky fonts.
And perhaps a maintainer generates PS files before building
a package, and put them in the package might be much safer,
I guess.
Best regards, 2002.3.8
--
Debian Developer & Debian JP Developer - much more I18N of Debian
Atsuhito Kohda <kohda@debian.org>
Department of Math., Tokushima Univ.
Reply to: