Recent texlive 2008 installed on Linux Slackware 12.0 system. I have a file that I can process via texexec and which shows up fine on my Acrobat Reader, kpdf or xpdf. However another person using (probably) Windows keeps getting corrupt file errors when he tries to read it. And when I try to run the output pdf through pdf2ps it blows up with this message: --------------------------------------------------------------------------------- **** Warning: An error occurred while reading an XREF table. **** The file has been damaged. This may have been caused **** by a problem while converting or transfering the file. **** Ghostscript will attempt to recover the data. ERROR: /undefined in /BXlevel Operand stack: 1 --dict:6/6(ro)(G)-- 8¬ÎµÈ¶dm Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push --nostringval-- %loop_continue --nostringval-- Dictionary stack: --dict:1119/1686(ro)(G)-- --dict:0/20(G)-- --dict:107/200 (L)-- --dict:107/200(L)-- --dict:104/127(ro) (G)-- --dict:241/347(ro)(G)-- --dict:18/24(L)-- Current allocation mode is local ESP Ghostscript 815.04: Unrecoverable error, exit code 1 --------------------------------------------------------------- Other pdf files on my system, built on other computers etc. process fine through pdf2ps. I took out all the advanced stuff, such as bookmarks, interaction and urls but I still get the same kind of error. An old pdf version of the file, dating back to February, also blows up. The preamble to the file plus dummy text looks like this: -------------------------------- \setupoutput[pdftex] \setupindenting[none] \setupwhitespace[medium] \frenchspacing \setupcolors[state=start] \setuphead[chapter][head=nomarking,number=no] \setuphead[section][number=no,textcommand=\bf] \setuphead[subsection][number=no] \setuphead[subsubsection][number=no] %\setupinteraction[state=start,color=blue] \setuplist[section][alternative=f,style=bold,interaction=no] \setuplist[subsection][alternative=f,interaction=no] \setuplist[subsubsection][alternative=c,interaction=no] \starttext foo \stoptext -------------- This blows up on pdf2ps also. I just created a dummy pdftex file, compiled it, then converted it with pdf2ps with no problem. Either there is an error in my preamble or something fishy with Context. Thoughts? -- John Culleton
On Fri, Sep 26, 2008 at 8:00 PM, John Culleton
Recent texlive 2008 installed on Linux Slackware 12.0 system.
I have a file that I can process via texexec and which shows up fine on my Acrobat Reader, kpdf or xpdf. However another person using (probably) Windows keeps getting corrupt file errors when he tries to read it. And when I try to run the output pdf through pdf2ps it blows up with this message:
--------------------------------------------------------------------------------- **** Warning: An error occurred while reading an XREF table. **** The file has been damaged. This may have been caused **** by a problem while converting or transfering the file. **** Ghostscript will attempt to recover the data. ERROR: /undefined in /BXlevel Operand stack: 1 --dict:6/6(ro)(G)-- 8¬ÎµÈ¶dm Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1 3 %oparray_pop 1 3 %oparray_pop 1 3 %oparray_pop --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push --nostringval-- %loop_continue --nostringval-- Dictionary stack: --dict:1119/1686(ro)(G)-- --dict:0/20(G)-- --dict:107/200 (L)-- --dict:107/200(L)-- --dict:104/127(ro) (G)-- --dict:241/347(ro)(G)-- --dict:18/24(L)--
Current allocation mode is local ESP Ghostscript 815.04: Unrecoverable error, exit code 1
maybe gs is too old. you can try with 8.61 or 8.62 or 8.63 (and cross the fingers ...) -- luigi
On Friday 26 September 2008 02:45:14 pm luigi scarso wrote:
maybe gs is too old. you can try with 8.61 or 8.62 or 8.63 (and cross the fingers ...)
I downloaded ghostscript 8.63 but the pdf2ps error persists. but the error goes away if I uses an earlier version of context, namely: TeXExec 5.2.4 - ConTeXt / PRAGMA ADE 1997-2005 (tetex distribution.) Therefore the problem lies in the recent Context I have been using, and not in ghostscript nor in my code. My curremt version of Context is: ConTeXt ver: 2008.05.21 15:21 MKII fmt: 2008.9.25 int: english/english The next previous version of Context I have also fails this test: ConTeXt ver: 2007.01.12 15:56 MKII fmt: 2007.9.26 int: english/english My test file at the moment is: \setupoutput[pdftex] \starttext foo \stoptext I am testing on LInux Slackware 12. Perhaps Hans or Thanh would care to comment. -- John Culleton Resources for every author and publisher: http://wexfordpress.com/tex/shortlist.pdf http://wexfordpress.com/tex/packagers.pdf http://www.creativemindspress.com/newbiefaq.htm http://www.gropenassoc.com/TopLevelPages/reference%20desk.htm
On Fri, Sep 26, 2008 at 11:29 PM, John Culleton
On Friday 26 September 2008 02:45:14 pm luigi scarso wrote:
maybe gs is too old. you can try with 8.61 or 8.62 or 8.63 (and cross the fingers ...)
I downloaded ghostscript 8.63 but the pdf2ps error persists. but the error goes away if I uses an earlier version of context, namely: TeXExec 5.2.4 - ConTeXt / PRAGMA ADE 1997-2005 (tetex distribution.) Therefore the problem lies in the recent Context I have been using, and not in ghostscript nor in my code.
Unfortunatly, I'm not sure about this. During these years I have discover bugs in pdftex/luatex but also in ghostoscript too; really, it seems that I have found another one this week in gs 8.63, but not in gs8.62 pdf spec. gs, luatex/context mkiv are moving target; three year ago the situation was a bit more stable. -- luigi PS Do you cross the fingers ?
Hi John, John Culleton wrote:
Therefore the problem lies in the recent Context I have been using, and not in ghostscript nor in my code.
I am fairly certain the bug will also go away if you start your new context documents with \pdfobjcompresslevel=0 or \pdfminorversion=4 as that automatically suppresses object compression, the number one cause of ghostscript issues with newer pdf files. Best wishes, Taco
On Fri, Sep 26, 2008 at 11:53 PM, Taco Hoekwater
Hi John,
John Culleton wrote:
Therefore the problem lies in the recent Context I have been using, and not in ghostscript nor in my code.
I am fairly certain the bug will also go away if you start your new context documents with
\pdfobjcompresslevel=0 or \pdfminorversion=4
\pdfminorversion=4 solve my problems with ghostscript at least from 2005; from 8.62, gs has some problems with fonts and rotate last page 90 clockwise or counter clockwise with some pdf . gs 8.63 works only with \pdfobjcompresslevel=0 (I mean, same problems of gs 8.62.)
as that automatically suppresses object compression, the number one cause of ghostscript issues with newer pdf files.
Not only with pdf, even in compilation. Starting from 8.62 I 'm not able to build libgs from source tree because there are some binaries that do not compile. I must compile ghostpdl, take these intermediary binaries (echogs, I believe, and some others) put them into ghostscript tree and recompile. Funny, after all. -- luigi
On Friday 26 September 2008 05:53:59 pm Taco Hoekwater wrote:
Hi John,
John Culleton wrote:
Therefore the problem lies in the recent Context I have been using, and not in ghostscript nor in my code.
I am fairly certain the bug will also go away if you start your new context documents with
\pdfobjcompresslevel=0 or \pdfminorversion=4
as that automatically suppresses object compression, the number one cause of ghostscript issues with newer pdf files.
Best wishes,
Bingo! Now I must try it with my original file and see if the other person I have mentioned still has trouble with reading the pdf I create. Thanks as always for the education. -- John Culleton Resources for every author and publisher: http://wexfordpress.com/tex/shortlist.pdf http://wexfordpress.com/tex/packagers.pdf http://www.creativemindspress.com/newbiefaq.htm http://www.gropenassoc.com/TopLevelPages/reference%20desk.htm
On Friday 26 September 2008 07:10:17 pm John Culleton wrote:
On Friday 26 September 2008 05:53:59 pm Taco Hoekwater wrote:
Hi John,
John Culleton wrote:
Therefore the problem lies in the recent Context I have been using, and not in ghostscript nor in my code.
I am fairly certain the bug will also go away if you start your new context documents with
\pdfobjcompresslevel=0 or \pdfminorversion=4
It turns out that the OP was using Acrobat 5, so it all fits together. Does the same command work with plain pdftex? -- John Culleton Resources for every author and publisher: http://wexfordpress.com/tex/shortlist.pdf http://wexfordpress.com/tex/packagers.pdf http://www.creativemindspress.com/newbiefaq.htm http://www.gropenassoc.com/TopLevelPages/reference%20desk.htm
participants (3)
-
John Culleton -
luigi scarso -
Taco Hoekwater