From: Gary P. <pa...@in...> - 2004-01-06 16:29:28
|
I've got PyX built and installed (I think) with the default options in setup.cfg I can run most of the files in the examples directory. But connect.py fails: --------------------------- C:\Python23\Lib\site-packages\pyx\examples>python connect.py Traceback (most recent call last): File "connect.py", line 7, in ? A = c.text(0,0, r"\bf A", text.halign.center, text.vshift.char(0.5)) AttributeError: class vshift has no attribute 'char' ------------------------- I can run *none* of the files in examples/graphs. They all fail trying to deal with TeX fonts, for example -------------------------- C:\Python23\Lib\site-packages\pyx\examples\graphs>python lissajous.py Error: module writet1 (file C:/tex/texmf/fonts/type1/bluesky/cm/cmsy10.pfb): unexpected end of file ==> Fatal error occurred, the output PDF file is not finished! -------------------------- I'm using the latest MikTeX and python 2.3.3 cmsy10.pfb exists at the location indicated any help? tia, gary |
From: Andre W. <wo...@us...> - 2004-01-06 21:28:25
|
Hi Gary, On 06.01.04, Gary Pajer wrote: > I can run most of the files in the examples directory. But connect.py > fails: > --------------------------- > C:\Python23\Lib\site-packages\pyx\examples>python connect.py > Traceback (most recent call last): > File "connect.py", line 7, in ? > A = c.text(0,0, r"\bf A", text.halign.center, text.vshift.char(0.5)) > AttributeError: class vshift has no attribute 'char' > ------------------------- You're running the CVS, aren't you? The vshift.char has gone in CVS, but not everything is up and running yet. I've just corrected this problem ... it's checked in, but you may need to wait up to 24 hours until sourceforges anonymous CVS mirror got the modifications. > I can run *none* of the files in examples/graphs. They all fail trying to > deal with TeX fonts, for example > -------------------------- > C:\Python23\Lib\site-packages\pyx\examples\graphs>python lissajous.py > > Error: module writet1 (file > C:/tex/texmf/fonts/type1/bluesky/cm/cmsy10.pfb): > unexpected end of file > ==> Fatal error occurred, the output PDF file is not finished! > -------------------------- Well, some of the graph examples didn't work eigher, but I've corrected them now as well. But some of the examples were ok already before my last checkins. And the message you observed is very confusing: it seems to come directly from within the writet1 extention module, which is build out of parts of the pdftex code (hence this wrong message about PDF output). Well, I don't yet see any reason, why these particular examples do not run while the other do. The graph module does nothing special in the usage of the text-module compared to those simple text examples in the root example directory. Could you copy the hello.py into the graph subdirectory and try to run it there? It might be, that some configuration problem prevents the examples to run at some locations ... lets first check that ... André -- by _ _ _ Dr. André Wobst / \ \ / ) wo...@us..., http://www.wobsta.de/ / _ \ \/\/ / PyX - High quality PostScript figures with Python & TeX (_/ \_)_/\_/ visit http://pyx.sourceforge.net/ |
From: Gary P. <pa...@in...> - 2004-01-07 01:47:20
|
> to those simple text examples in the root example directory. Could you > copy the hello.py into the graph subdirectory and try to run it there? > It might be, that some configuration problem prevents the examples to > run at some locations ... lets first check that ... The problem is directory-independent. And hello.py doesn't work ... it gives the same error. In fact, all of the examples that involve text produce the error. The ones that are graphics-only are ok. How can I help debug? -gary |
From: Andre W. <wo...@us...> - 2004-01-07 17:11:21
|
Hi Gary, On 06.01.04, Gary Pajer wrote: > In fact, all of the examples that involve text produce the error. The ones > that are graphics-only are ok. > > How can I help debug? Could you first try to run a small example in pdftex? (The code ommitting the error is taken from pdftex, hence let us first try if pdftex is broken in your setup as well.) Please save the following code Hello, world! \bye in a file and run pdftex <filename>. Please send us the pdftex output written to the console and the pyx output when running hello.py. André -- by _ _ _ Dr. André Wobst / \ \ / ) wo...@us..., http://www.wobsta.de/ / _ \ \/\/ / PyX - High quality PostScript figures with Python & TeX (_/ \_)_/\_/ visit http://pyx.sourceforge.net/ |
From: Gary P. <pa...@in...> - 2004-01-07 20:45:32
|
> > How can I help debug? > > Could you first try to run a small example in pdftex? (The code > ommitting the error is taken from pdftex, hence let us first try if > pdftex is broken in your setup as well.) Please save the following code > > Hello, world! > \bye > > in a file and run pdftex <filename>. Please send us the pdftex output > written to the console and the pyx output when running hello.py. 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. |
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/ |
From: Gary P. <pa...@in...> - 2004-01-10 16:28:43
|
Hello, Andre [...] > > 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. [...] > 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. > No additional info there. > 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") This works perfectly > > If this works, my guess is, that you're opening the pfb in ascii > instead of binary mode in writet1.c. How do we try to fix it? I took a quick look at stript1.c, but I don't speak c very well ... Did I mention that I'm using the Mingw compiler? (FWIW) -gary |
From: Andre W. <wo...@us...> - 2004-01-12 06:45:43
|
Hi Gary, On 11.01.04, Gary Pajer wrote: > I rebuilt PyX from scratch with the flag in setup.cfg set to 0. > I tried several examples, and they all work fine. > (I thought I had tried this earlier, but I must have done something > incorrectly that time.) Well, there was another fallback solution when disabling the t1strip C extention module, which relied on a external program (pfbtopfa). You needed to have this executable around. You probably didn't had that (its quite likely that this executable is not arround, so our old fallback solution was kind of bad ... ;-)). Now I wrote this pure python replacement (fullfont), since the task of converting pfb to pfa is really trivial. The question is now, if we should disable this C extention module by default. This would help people in setting up PyX without needing to compile any C extention modules by default. > > #define search(a, b, c) (fopen(b, "rb")) > > Did this and rebuilt. > I tried several examples, and they all work fine. Fine. I've just checked in this correction. Thanks a lot for your patience in bringing up and solving this subject. > Interesting: the eps files are indeed smaller ... connect.eps goes from 53 > kB to 8 kB This means that this example consists mainly out of fonts ... ;-) > But the pdf's that I make from the eps's are both the same size ... 4 kB. > (Just a curious note.) Well, it's not that curious. It seems to be, that your ps to pdf converter does strip the fonts itself canceling all glyphs not needed. André -- by _ _ _ Dr. André Wobst / \ \ / ) wo...@us..., http://www.wobsta.de/ / _ \ \/\/ / PyX - High quality PostScript figures with Python & TeX (_/ \_)_/\_/ visit http://pyx.sourceforge.net/ |
From: Gary P. <pa...@in...> - 2004-01-12 12:34:09
|
> The question is now, if we should disable this C extention module by > default. This would help people in setting up PyX without needing to > compile any C extention modules by default. I don't know what all the issues are, but certainly most Windows users don't have a compiler. -g |