From: Andre W. <wo...@us...> - 2006-05-11 10:32:08
|
Hi, On 11.05.06, Arnd Baecker wrote: > http://www.physik.tu-dresden.de/~baecker/tmp/pyx_embed/pyx_embed_prob.ps > > When trying to display page 3 of this file with gv > a longish ghostscript error messages appears, I have this problem here too and it does not depend on ghostscript at all. (Somebody else already reported, that it works for him on the gs command line but not within gv. As for me. And I've tried several gs's.) What I than did was to create a simple script "mygs", which contains a line like "tee mygs.out|gs @$" and configured ghostview to use this script. (BTW I have a gv 3.5.8 from fink here.) You can than try to run the created mygs.out file on gs and than you also get the on the gs command line. Now comes the interesting part of what's different between the orginial and the mygs.out file. Here comes the diff: andre@pb:~$ diff -u pyx_embed_prob.ps mygs.out |head -40 --- pyx_embed_prob.ps Thu May 11 07:47:01 2006 +++ mygs.out Thu May 11 11:39:01 2006 @@ -1,12 +1,3 @@ -%!PS-Adobe-2.0 -%%Creator: dvips(k) 5.92b Copyright 2002 Radical Eye Software -%%Title: pyx_embed_prob.dvi -%%Pages: 3 -%%PageOrder: Ascend -%%BoundingBox: 0 0 596 842 -%%DocumentFonts: CMBX12 CMR10 CMTI9 CMR9 CMR8 CMBX9 CMMI10 CMEX10 CMR7 -%%+ CMMI7 CMBX10 CMSY10 CMR5 CMSY7 CMMI9 CMR6 CMSY9 CMTT9 -%%EndComments %DVIPSWebPage: (www.radicaleye.com) %DVIPSCommandLine: dvips pyx_embed_prob %DVIPSParameters: dpi=600, compressed @@ -9511,254 +9502,3 @@ 1,:U?1,:U?1,:U?1,:U?1,:U?1,:U?1,:U?1,:U?1,:U?1,AmF!"fJ:!<J8a!?qLF&HMtG!WU(< *rl9A"T\W)!<E3$!!!!!!!!!"!WrQ/"pYD?$4HmP!4<@<!W`B*!X&T/"U"r.!!.KK!WrE*&Hrdj 0gQ!W;.0\RE>10ZOeE%*6F"?A;UOtZ1LbBV#mqFa(`=5<-7:2j.Ps"@2`NfY6UX@47n?3D;cHat -='/U/@q9._B4u!oF*)PJGBeCZK7nr5LPUeEP*;,qQC!u,R\HRQV5C/hWN*81['d?O\@K2f_o0O6 -a2lBFdaQ^rf%8R-g>V&OjQ5OekiqC&o(2MHp@n@XqZ"J6*ru?D!<E3%!<E3%!<<*"!!!!"!WrQ/ -"pYD?$4HmP!4<C=!W`?*"9Sc3"U"r.!<RHF!<N?8"9fr'"qj4!#@VTc+u4]T'LIqUZ,$_k1K*]W -@WKj'(*k`q-1Mcg)&ahL-n-W'2E*TU3^Z;(7Rp!@8lJ\h<``C+>%;)SAnPdkC3+K>G'A1VH@gd& -KnbA=M2II[Pa.Q$R$jD;USO``Vl6SpZEppG[^WcW]#)A'`Q#s>ai`&\eCE.%f\,!<j5f=akNM0q -o(2MHp@n@XqZ#7L$j-M1!YGMH!'^JXqC&(g$H;O"r.3r,5P-7rMVAU<B_mTj*t[:Ya4(#0b--&: -r^*mh5Pb\\MY=%L!6FS8j-SoPhsgV8fq'/_!08Q.!$C?=HAX5m`;]fQ7Zl=OU5H`p72/Q!72/Q! -72/Q!72/Q!72/Q!72/Q!72/Q!72/Q!72/Q!72/Q!72/Q!72/Q!72/Q!72/Q!72/Q!72/Q!72/Q! -72/Q!72/Q!72/Q's4I~> -%%EndData -grestore -gsave -gsave -/DeviceRGB setcolorspace -<< -/ImageType 1 -/Width 2 -/Height 256 -/BitsPerComponent 8 -/ImageMatrix [0.094074 0.000000 -0.000000 -4.515556 -78.666667 320.000000] -/Decode [0 1 0 1 0 1] I've cut the rest of the code from pyx_embed_prob.ps ... the mygs.out is just missing all the rest. So somewho gv does stop sending the data to ghostscript. I'm not yet sure whether this is due to the content of the lines involved. Maybe somebody of you might see, what could stop gv from sending further lines. I have no idea. All that happens in a ASCII85 encoded part of the file, but there are proper DSC's around that part to skip it in the DSC parsing process. A solution might be to not use the ASCII85 encoding but a hex encoding and try again. I can prepare a patch for the bitmap module to use a different filter with only having hexadecimal code in the Postscript (which of course would become bigger by that, since ASCII85 encodes 4 bytes into 5, whereas a hex encoder would encode 1 byte into 2). Maybe somebody want's to have a look into the gv code. I don't really want ... :-) André -- by _ _ _ Dr. André Wobst / \ \ / ) wo...@us..., http://www.wobsta.de/ / _ \ \/\/ / PyX - High quality PostScript and PDF figures (_/ \_)_/\_/ with Python & TeX: visit http://pyx.sourceforge.net/ |