On 19.07.05, Joerg Lehmann wrote:
> On 19.07.05, Eugene M. Minkovskii wrote:
> > In the file pykpathsea/__init__.py I found that you search
> > psfonts.map using command kpsewhich psfonts.map
> > This command from command line return following:
> > /home/emin/.texmf-var/fonts/map/dvips/updmap/psfonts.map
From the `latex -version` I expect that you are using teTeX 3.0, is
this correct? In teTeX 3.0 the standard paths to search for a
psfonts.map is (something like)
where the first entries contain the user's trees and the
second line the system trees
> This file exist but don't contain cmr10 font in it
This is the problem. You will find a the file
Please make sure that the cmr fonts of type1 are included there. Then,
And follow the output to find the corresponding map-file for these
fonts. Then, both, your latex and PyX will find your fonts.
> > $ grep cmr10 `locate psfonts.map`
> > /usr/local/share/texmf-var/fonts/map/dvips/updmap/psfonts.map:cmr10 CMR10 <cmr10.pfb
> > If I run latex and then run dvips, dvips found information about
> > cmr10 in file /usr/local/share/texmf-var/fonts/map/dvips/updmap/psfonts.map
> This means that your dvips is not using the same kpathsearch library as
> your kpsewhich program. If you have linked the kpathsearch library
> dynamically you can actually find out whether this is the case or not.
This sounds like a bug in the TeX distribution. If the problem still
persists after the updmap then consider filing a bug against the TeX
> > Perhaps your program must search all of possible psfonts.map
> > files in same order as dvips?
> It should of course do, as it is using exactly the same mechanism. The
> search order is configured in the texmf.cnf file which you should find
> at the root of your texmf tree.
"A mathematician is a device for turning coffee into theorems"