Re: error 109 in wholesite.pdf
Johannes Schaefer schrieb:
> Hi!
>
> Has anybody seen this Acrobat Reader 7.0 error message?
>
> "There was an error processing this page.
> There was a problem reading this document (109)"
Curiosity: the outline ("Bookmarks" in Acrobat slang)
is displayed correctly. There are 515 pages.
> We have a fairly large PDF generated for our complete
> documentation (a styleguide), about 7.5M. It displays
> in Acrobat 4.0 but not in 7.0. It was created using
> forrest 0.6 with some changes to document2fo.xsl.
>
> First look with google:
> Might be memory? Weird characters?
>
> Will have a closer look now,
> any hint appreciated.
>
> Johannes
>
>
>
>
>
>
>
>
--
User Interface Design GmbH * Teinacher Str. 38 * D-71634 Ludwigsburg
Fon +49 (0)7141 377 000 * Fax +49 (0)7141 377 00-99
Geschäftsstelle: User Interface Design GmbH * Lehrer-Götz-Weg 11 * D-81825
München
www.uidesign.de
Buch "User Interface Tuning" von Joachim Machate & Michael Burmester
www.user-interface-tuning.de
Re: error 109 in wholesite.pdf
the single-page pdfs are working correctly
js
Johannes Schaefer schrieb:
> Johannes Schaefer schrieb:
>
>>Hi!
>>
>>Has anybody seen this Acrobat Reader 7.0 error message?
>>
>>"There was an error processing this page.
>> There was a problem reading this document (109)"
>
>
> Curiosity: the outline ("Bookmarks" in Acrobat slang)
> is displayed correctly. There are 515 pages.
>
>
>>We have a fairly large PDF generated for our complete
>>documentation (a styleguide), about 7.5M. It displays
>>in Acrobat 4.0 but not in 7.0. It was created using
>>forrest 0.6 with some changes to document2fo.xsl.
>>
>>First look with google:
>> Might be memory? Weird characters?
>>
>>Will have a closer look now,
>>any hint appreciated.
>>
>>Johannes
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
--
User Interface Design GmbH * Teinacher Str. 38 * D-71634 Ludwigsburg
Fon +49 (0)7141 377 000 * Fax +49 (0)7141 377 00-99
Geschäftsstelle: User Interface Design GmbH * Lehrer-Götz-Weg 11 * D-81825
München
www.uidesign.de
Buch "User Interface Tuning" von Joachim Machate & Michael Burmester
www.user-interface-tuning.de
Re: error 109 in wholesite.pdf
http://marc.theaimsgroup.com/?t=11249790443&r=1&w=2 HTH salu2 On Fri, 2005-09-02 at 10:11 +0200, Johannes Schaefer wrote: > Hi! > > Has anybody seen this Acrobat Reader 7.0 error message? > > "There was an error processing this page. > There was a problem reading this document (109)" > > We have a fairly large PDF generated for our complete > documentation (a styleguide), about 7.5M. It displays > in Acrobat 4.0 but not in 7.0. It was created using > forrest 0.6 with some changes to document2fo.xsl. > > First look with google: > Might be memory? Weird characters? > > Will have a closer look now, > any hint appreciated. > > Johannes > > > > > > > > -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
Re: error 109 in wholesite.pdf
Thanks, Thorsten! The problem is not viewing the file from a Browser (whatsoever): I get this error opening the statically generated (forrest site) wholesite.pdf with the standalone Acrobat Reader 7.0.3 (now with the latest updates, too). Johannes Thorsten Scherler schrieb: > http://marc.theaimsgroup.com/?t=11249790443&r=1&w=2 > > HTH > salu2 > > On Fri, 2005-09-02 at 10:11 +0200, Johannes Schaefer wrote: > >>Hi! >> >>Has anybody seen this Acrobat Reader 7.0 error message? >> >>"There was an error processing this page. >> There was a problem reading this document (109)" >> >>We have a fairly large PDF generated for our complete >>documentation (a styleguide), about 7.5M. It displays >>in Acrobat 4.0 but not in 7.0. It was created using >>forrest 0.6 with some changes to document2fo.xsl. >> >>First look with google: >> Might be memory? Weird characters? >> >>Will have a closer look now, >>any hint appreciated. >> >>Johannes >> >> >> >> >> >> >> >> -- User Interface Design GmbH * Teinacher Str. 38 * D-71634 Ludwigsburg Fon +49 (0)7141 377 000 * Fax +49 (0)7141 377 00-99 Geschäftsstelle: User Interface Design GmbH * Lehrer-Götz-Weg 11 * D-81825 München www.uidesign.de Buch "User Interface Tuning" von Joachim Machate & Michael Burmester www.user-interface-tuning.de
Re: error 109 in wholesite.pdf
On Fri, 2005-09-02 at 12:08 +0200, Johannes Schaefer wrote: > Thanks, Thorsten! > > The problem is not viewing the file from a Browser > (whatsoever): I get this error opening the statically > generated (forrest site) wholesite.pdf with the > standalone Acrobat Reader 7.0.3 (now with the latest > updates, too). > hmm, the old version of the reader is still working with the pdf? If not then it has to be something in the docs that causes it (check your svn/cvs). If it does check the change log of the reader. salu2 -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
Re: error 109 in wholesite.pdf
On Friday September 02 2005 6:31 am, Thorsten Scherler wrote: > On Fri, 2005-09-02 at 12:08 +0200, Johannes Schaefer wrote: > > Thanks, Thorsten! > > > > The problem is not viewing the file from a Browser > > (whatsoever): I get this error opening the statically > > generated (forrest site) wholesite.pdf with the > > standalone Acrobat Reader 7.0.3 (now with the latest > > updates, too). > > hmm, the old version of the reader is still working with the pdf? > If not then it has to be something in the docs that causes it (check > your svn/cvs). If it does check the change log of the reader. I don't really have much in the way of real help but AR 6 and 7 are less tolerant of errors than the older readers were, so it is possible to have a file that renders fine in the old one but the new one balks at something. I know nothing about Forrest's PDF generation process but I have seen others say that upgrading their version of GhostScript have made these kinds of errors go away. - Addi
Re: error 109 in wholesite.pdf
Acrobat Reader 4.0 "barks" as well, but only on single pages (which at least gives us a clue!). I think we drilled it down to some (a lot that is!) PNG images ... will let you know when we're sure. Johannes addi schrieb: > On Friday September 02 2005 6:31 am, Thorsten Scherler wrote: > >>On Fri, 2005-09-02 at 12:08 +0200, Johannes Schaefer wrote: >> >>>Thanks, Thorsten! >>> >>>The problem is not viewing the file from a Browser >>>(whatsoever): I get this error opening the statically >>>generated (forrest site) wholesite.pdf with the >>>standalone Acrobat Reader 7.0.3 (now with the latest >>>updates, too). >> >>hmm, the old version of the reader is still working with the pdf? >>If not then it has to be something in the docs that causes it (check >>your svn/cvs). If it does check the change log of the reader. > > > I don't really have much in the way of real help but AR 6 and 7 are less > tolerant of errors than the older readers were, so it is possible to have a > file that renders fine in the old one but the new one balks at something. > > I know nothing about Forrest's PDF generation process but I have seen others > say that upgrading their version of GhostScript have made these kinds of > errors go away. > > - Addi > -- User Interface Design GmbH * Teinacher Str. 38 * D-71634 Ludwigsburg Fon +49 (0)7141 377 000 * Fax +49 (0)7141 377 00-99 Geschäftsstelle: User Interface Design GmbH * Lehrer-Götz-Weg 11 * D-81825 München www.uidesign.de Buch "User Interface Tuning" von Joachim Machate & Michael Burmester www.user-interface-tuning.de
Re: error 109 in wholesite.pdf
This is a rather weird thing. The error seems to be caused by PNG images that were directly written from Photoshop (export for web). After converting them with irfanview from PNG to PNG the PDF works fine again. BTW: the PNGs become a little bit smaller as well. The single page PDFs did *not* work, we just could not locate them (with AR4 it was much easier). Don't have a clue, why AR is barking at those PNGs, esp. since both programs are Adobe ... but now: be warned! Cheers Johannes Johannes Schaefer schrieb: > Acrobat Reader 4.0 "barks" as well, but only on > single pages (which at least gives us a clue!). > I think we drilled it down to some (a lot that > is!) PNG images ... > > will let you know when we're sure. > > Johannes > > addi schrieb: > >>On Friday September 02 2005 6:31 am, Thorsten Scherler wrote: >> >> >>>On Fri, 2005-09-02 at 12:08 +0200, Johannes Schaefer wrote: >>> >>> Thanks, Thorsten! The problem is not viewing the file from a Browser (whatsoever): I get this error opening the statically generated (forrest site) wholesite.pdf with the standalone Acrobat Reader 7.0.3 (now with the latest updates, too). >>> >>>hmm, the old version of the reader is still working with the pdf? >>>If not then it has to be something in the docs that causes it (check >>>your svn/cvs). If it does check the change log of the reader. >> >> >>I don't really have much in the way of real help but AR 6 and 7 are less >>tolerant of errors than the older readers were, so it is possible to have a >>file that renders fine in the old one but the new one balks at something. >> >>I know nothing about Forrest's PDF generation process but I have seen others >>say that upgrading their version of GhostScript have made these kinds of >>errors go away. >> >>- Addi >> > > > -- User Interface Design GmbH * Teinacher Str. 38 * D-71634 Ludwigsburg Fon +49 (0)7141 377 000 * Fax +49 (0)7141 377 00-99 Geschäftsstelle: User Interface Design GmbH * Lehrer-Götz-Weg 11 * D-81825 München www.uidesign.de Buch "User Interface Tuning" von Joachim Machate & Michael Burmester www.user-interface-tuning.de
Re: error 109 in wholesite.pdf
This is a rather weird thing. The error seems to be caused by PNG images that were directly written from Photoshop (export for web). After converting them with irfanview from PNG to PNG the PDF works fine again. BTW: the PNGs become a little bit smaller as well. The single page PDFs did *not* work, we just could not locate them (with AR4 it was much easier). Don't have a clue, why AR is barking at those PNGs, esp. since both programs are Adobe ... but now: be warned! Cheers Johannes Johannes Schaefer schrieb: > Acrobat Reader 4.0 "barks" as well, but only on > single pages (which at least gives us a clue!). > I think we drilled it down to some (a lot that > is!) PNG images ... > > will let you know when we're sure. > > Johannes > > addi schrieb: > >>On Friday September 02 2005 6:31 am, Thorsten Scherler wrote: >> >> >>>On Fri, 2005-09-02 at 12:08 +0200, Johannes Schaefer wrote: >>> >>> Thanks, Thorsten! The problem is not viewing the file from a Browser (whatsoever): I get this error opening the statically generated (forrest site) wholesite.pdf with the standalone Acrobat Reader 7.0.3 (now with the latest updates, too). >>> >>>hmm, the old version of the reader is still working with the pdf? >>>If not then it has to be something in the docs that causes it (check >>>your svn/cvs). If it does check the change log of the reader. >> >> >>I don't really have much in the way of real help but AR 6 and 7 are less >>tolerant of errors than the older readers were, so it is possible to have a >>file that renders fine in the old one but the new one balks at something. >> >>I know nothing about Forrest's PDF generation process but I have seen others >>say that upgrading their version of GhostScript have made these kinds of >>errors go away. >> >>- Addi >> > > > -- User Interface Design GmbH * Teinacher Str. 38 * D-71634 Ludwigsburg Fon +49 (0)7141 377 000 * Fax +49 (0)7141 377 00-99 Geschäftsstelle: User Interface Design GmbH * Lehrer-Götz-Weg 11 * D-81825 München www.uidesign.de Buch "User Interface Tuning" von Joachim Machate & Michael Burmester www.user-interface-tuning.de
