hefronmedia / pdfsizeopt

Automatically exported from code.google.com/p/pdfsizeopt
0 stars 0 forks source link

AssertionError: Type1CParser failed (status) #34

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
``Labels: Optimize-''

What command do you run to optimize the PDF?

python2.6 pdfsizeopt.py --use-pngout=true --use-jbig2=true --use-
multivalent=true  reign-company-reference.pdf

(It does not work with either or all of the options set to false, either)

What does pdfsizeopt display when running the command above?

info: This is pdfsizeopt.py r134.
info: loading PDF from: reign-company-reference.pdf
info: loaded PDF of 351907 bytes
info: separated to 39 objs
info: found 4 Type1 fonts loaded
info: writing Type1CConverter (340427 font bytes) to: pso.conv.tmp.ps
info: executing Type1CConverter with Ghostscript: gs -q -dNOPAUSE -dBATCH -
sDEVICE=pdfwrite -dPDFSETTINGS=/printer -
dColorConversionStrategy=/LeaveColorUnchanged -sOutputFile=pso.conv.tmp.pdf 
-f pso.conv.tmp.ps
Type1CConverter: using interpreter GPL Ghostscript 864 20090203
Type1CConverter: converting font /EEWDVQ+LinBiolinumB to /Obj0000000028
Type1CConverter: converting font /LIADQI+LinLibertineB to /Obj0000000030
Type1CConverter: converting font /DQKHPE+LinLibertine to /Obj0000000032
Type1CConverter: converting font /ZVZAAW+LinLibertineI to /Obj0000000034
Type1CConverter: all OK
info: loading PDF from: pso.conv.tmp.pdf
info: loaded PDF of 26209 bytes
info: separated to 29 objs
info: found 4 fonts in GS output
info: optimized total Type1 font size 340457 to Type1C font size 17757 (5%)
info: optimized Type1 font XObject 32,31: new size=7584 (8%)
info: optimized Type1 font XObject 34,33: new size=4210 (6%)
info: optimized Type1 font XObject 28,27: new size=4079 (6%)
info: optimized Type1 font XObject 30,29: new size=3255 (3%)
info: found 4 Type1C fonts loaded
info: writing Type1CParser (17679 font bytes) to: pso.conv.parse.tmp.ps
info: executing Type1CParser with Ghostscript: gs -q -dNOPAUSE -dBATCH -
sDEVICE=nullpage -sDataFile=pso.conv.parsedata.tmp.ps -f 
pso.conv.parse.tmp.ps
Type1CParser: using interpreter GPL Ghostscript 864 20090203
Error: /typecheck in --closefile--
Operand stack:
   --nostringval--   --dict:3/3(L)--   --nostringval--   --dict:1/1(ro)(L)-
-
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --
nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --
nostringval--   false   1   %stopped_push   1862   1   3   %oparray_pop   
1861   1   3   %oparray_pop   1845   1   3   %oparray_pop   1739   1   3   
%oparray_pop   --nostringval--   %errorexec_pop   .runexec2   --
nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --
nostringval--   --nostringval--
Dictionary stack:
   --dict:1147/1684(ro)(G)--   --dict:0/20(G)--   --dict:87/200(L)--
Current allocation mode is local
Last OS error: 2
Current file position is 12115
GPL Ghostscript 8.64: Unrecoverable error, exit code 1
info: Type1CParser failed, status=0x100
Traceback (most recent call last):
  File "pdfsizeopt.py", line 6157, in <module>
    main(sys.argv)
  File "pdfsizeopt.py", line 6140, in main
    do_regenerate_all_fonts=do_regenerate_all_fonts)
  File "pdfsizeopt.py", line 4261, in UnifyType1CFonts
    data_tmp_file_name='pso.conv.parsedata.tmp.ps')
  File "pdfsizeopt.py", line 3998, in ParseType1CFonts
    assert 0, 'Type1CParser failed (status)'
AssertionError: Type1CParser failed (status)

What's wrong with the optimized PDF?

The parsing breaks and no optimized PDF is created at all.

What should be there in the optimized PDF instead?

There should be one in the first place. (If the info is helpful: The PDF 
was created with pdfTeX, Version 3.1415926-1.40.10 (TeX Live 2009))

Original issue reported on code.google.com by belch...@googlemail.com on 4 Apr 2010 at 1:35

Attachments:

GoogleCodeExporter commented 9 years ago
Can you try the patch that I posted for issue 31?

Original comment by william.bader@gmail.com on 13 Apr 2010 at 5:18

GoogleCodeExporter commented 9 years ago
With that patch applied the PDF is correctly optimized. I will try some more 
files 
that caused trouble, but so far they seem all to work now. Thanks!

Original comment by belch...@googlemail.com on 13 Apr 2010 at 6:10

GoogleCodeExporter commented 9 years ago
Thank you for reporting this bug. Integrated William's patch to fix the bug. 
r143 works fine.

Original comment by pts...@gmail.com on 10 Feb 2011 at 9:11