From: Andre W. <wo...@us...> - 2004-01-09 07:16:36
|
Hi Gary, On 07.01.04, Gary Pajer wrote: > My pleasure: > > C:\Python23\Lib\site-packages\pyx\examples>pdftex helloworld.tex > This is pdfTeX, Version 3.141592-1.11b (MiKTeX 2.4) > (helloworld.tex{pdftex.cfg} [1{psfonts.map}] )<cmr10.pfb> > Output written on helloworld.pdf (1 page, 7341 bytes). > Transcript written on helloworld.log. > > and > > C:\Python23\Lib\site-packages\pyx\examples>python hello.py > > Error: module writet1 (file C:/tex/texmf/fonts/type1/bluesky/cm/cmr10.pfb): > unex > pected end of file > ==> Fatal error occurred, the output PDF file is not finished! > > helloworld.pdf is perfect. I thought we could see some path names from the pdftex output (which was the case on the installation, I tried the example myself, but this seems to be depending on the TeX distribution). However, I've written a pfbtopfa converter in pure python now and checked it into the CVS. 1. Can you try to look into the helloworld.log from the pdftex run and see, if there are path names in it? Just to make sure, that you are using this same pfb font in pdftex and in PyX). I know, they really should be the same, but lets check this first. 2. Can you try my new pfbtopfa converter to read the cmr10.pfb on your system? Just fetch the latest CVS and step into the directory pyx/t1strip (you may have to wait some hours until it becomes available for anonymous checkout). Then try the following: andre@pb:~/python/pyx/pyx/t1strip$ python Python 2.3 (#1, Sep 13 2003, 00:49:11) [GCC 3.3 20030304 (Apple Computer, Inc. build 1495)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from fullfont import fullfont >>> fullfont(open("cmr10.pfa", "w"), "/sw/share/texmf/fonts/type1/bluesky/cm/cmr10.pfb") You have to replace the "/sw/share/.../cmr10.pfb" with your location "C:\tex\texmf\...\cmr10.pfb". This fullfont function should run without omitting any messages. It should create the full cmr10.pfa in the local directory. If this works, my guess is, that you're opening the pfb in ascii instead of binary mode in writet1.c. If it does not work, could you please mail me your cmr10.pfb (you may mail it directly to me, not over the list). André PS: Jörg: I've just replaced the old fallback solution when turning off the building of the binary extention module t1strip. We may set this to be the default in setup.cfg. People could then install PyX without compiling anything. They would just need a proper TeX environment. The binary modules with the ability to strip the fonts would be for real man ... as we decided it for libkpathsea as well already ... -- by _ _ _ Dr. André Wobst / \ \ / ) wo...@us..., http://www.wobsta.de/ / _ \ \/\/ / PyX - High quality PostScript figures with Python & TeX (_/ \_)_/\_/ visit http://pyx.sourceforge.net/ |