From: Thomas P. <tho...@in...> - 2005-05-19 09:25:38
|
Hiho, PyX tends to produce rather large EPS files. Does anybody know of a simple way to compress these files? I don't mean some external compression like gzip. 'eps2eps' (which basically is a wrapper script for 'gs') shrinks the EPS size, but also in a literal sense: bounding boxes with negative starting points get truncated to the positive quadrant, so it's not really an option. Cheers, Tom -- Thomas Pohl, Lehrstuhl fuer Informatik X (Systemsimulation), Universitaet Erlangen, Cauerstr. 6, D-91058 Erlangen, Germany phone: +49(0)9131 85-28687 fax: +49(0)9131 85-28928 url: http://www10.informatik.uni-erlangen.de/~pohlt/ |
From: Arnd B. <arn...@we...> - 2005-05-19 09:35:58
|
Hi Thomas, On Thu, 19 May 2005, Thomas Pohl wrote: > Hiho, > PyX tends to produce rather large EPS files. Hmm, this is a rather general statement - which I cannot confirm - most of the plots I generate with PyX are very small. Maybe you can post a small stand-alone example? Best, Arnd |
From: Andre W. <wo...@us...> - 2005-05-19 10:10:54
|
Hi, On 19.05.05, Arnd Baecker wrote: > On Thu, 19 May 2005, Thomas Pohl wrote: > > Hiho, > > PyX tends to produce rather large EPS files. > > Hmm, this is a rather general statement - which I cannot > confirm - most of the plots I generate with PyX > are very small. > Maybe you can post a small stand-alone example? A generic problem is, that people might not strip the fonts down to the glyphs they use, but include full fonts. This will go away once we have a pure python implementation for t1strip. Currently we use some parts of the pdftex code for font stripping, but building this c-extension module is optional and turned off by default. 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: Thomas P. <tho...@in...> - 2005-05-19 11:09:07
|
Of course you are right. The statement is rather general. I compared the file sizes to the ones I get from CreEPS ('my' C++ tool with similar purpose, but I cannot longer recommend it since I learned about PyX ;-/). I just had a look at the files generated with PyX and noticed some issues: * All Postscript key words are used in their native form, i.e., not abbreviated. * The selectfont command always comes in pairs, e.g., /Palatino-Roman-TeXBase1Encoding 9.962640 selectfont /Palatino-Roman-TeXBase1Encoding 9.962640 selectfont * Many redundant gsave/grestore commands. I know from coding CreEPS that this is hard to avoid. PyX is great! Actually, I like PyX so much, that I'm no longer using my own CreEPS library... So I'm not complaining by any means, just trying to make you think about saving some file size. :-) Cheers, Tom Arnd Baecker wrote: > Hi Thomas, > > On Thu, 19 May 2005, Thomas Pohl wrote: > > >>Hiho, >>PyX tends to produce rather large EPS files. > > > Hmm, this is a rather general statement - which I cannot > confirm - most of the plots I generate with PyX > are very small. > Maybe you can post a small stand-alone example? > > Best, > > Arnd > > -- Thomas Pohl, Lehrstuhl fuer Informatik X (Systemsimulation), Universitaet Erlangen, Cauerstr. 6, D-91058 Erlangen, Germany phone: +49(0)9131 85-28687 fax: +49(0)9131 85-28928 url: http://www10.informatik.uni-erlangen.de/~pohlt/ |
From: Joerg L. <jo...@us...> - 2005-05-19 14:29:14
|
Hi Tom, On 19.05.05, Thomas Pohl wrote: > Of course you are right. The statement is > rather general. I compared the file sizes > to the ones I get from CreEPS ('my' C++ tool > with similar purpose, but I cannot longer > recommend it since I learned about PyX ;-/). > > I just had a look at the files generated with PyX > and noticed some issues: > > * All Postscript key words are used in their native > form, i.e., not abbreviated. We always wanted to keep the PS files readable, that's why we have never used any abbreviations. > * The selectfont command always comes in pairs, e.g., > /Palatino-Roman-TeXBase1Encoding 9.962640 selectfont > /Palatino-Roman-TeXBase1Encoding 9.962640 selectfont That's something which should be not happen. I remember that recently (well a few months ago, but still after the release of PyX 0.7.1), there was a change in the dvifile code, which probably fixes this problem. > * Many redundant gsave/grestore commands. I know from > coding CreEPS that this is hard to avoid. Yes, at the moment, we cannot avoid that. > PyX is great! Actually, I like PyX so much, that I'm no > longer using my own CreEPS library... So I'm not > complaining by any means, just trying to make you think > about saving some file size. :-) Thanks. Btw, in the future, when the corresponding code will be finished, using PDF as output format will probably give the ultimate reduction of file sizes, especially when you enable compression. Jörg |
From: Andre W. <wo...@us...> - 2005-05-19 10:13:46
|
Hi, On 19.05.05, Thomas Pohl wrote: > 'eps2eps' (which basically is a wrapper script > for 'gs') shrinks the EPS size, but also in a literal > sense: bounding boxes with negative starting points get > truncated to the positive quadrant, so it's not really > an option. You can provide a paper format in writeEPSfile. PyX will then center the output on that page while the file remains useable EPS. When the page size is large enough, the whole bounding box will be positive. André -- by _ _ _ Dr. André Wobst / \ \ / ) wo...@us..., http://www.wobsta.de/ / _ \ \/\/ / PyX - High quality PostScript figures with Python & TeX (_/ \_)_/\_/ visit http://pyx.sourceforge.net/ |