[privoxy-devel] [ ijbswa-Bugs-711668 ] Broken PDFs with OS/2

[SourceForge.net <no...@so...>]

Bugs item #711668, was opened at 2003-03-28 21:28
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=111118&aid=711668&group_id=11118

Category: os2-specific
Group: version 3.0
Status: Open
Resolution: Accepted
Priority: 5
Submitted By: David Mediavilla (davidme)
Assigned to: David Schmidt (david__schmidt)
Summary: Broken PDFs with OS/2

Initial Comment:
After installing 3.0.2  for OS/2, the  documentation
PDFs are broken. The files are:

25/08/02  19:41         124.685           0 
privoxy-developer-manual.pdf
25/08/02  19:41         124.285           0 
privoxy-faq.pdf
25/08/02  19:41         334.316           0 
privoxy-user-manual.pdf


GSView 4.0  with ChostScript 7.0.3 tells that the error
is :

Scanning PDF file
Unrecoverable error: syntaxerror in readxref

Acrobat 3.0 simply says that there is an irrecoverable
error.

----------------------------------------------------------------------

>Comment By: Hal Burgiss (hal9)
Date: 2003-03-29 18:46

Message:
Logged In: YES 
user_id=322640

First, I am committing fresh PDFs to cvs. Sorry David, or
anyone that was depending on these.

I thought we had had this conversation before and decided to
move away from keeping docs in cvs, and in fact, had decided
that PDF docs would be kept on the website (and not cvs).
But maybe not ;-) 

OES, your proposal sounds fine to me, but I'd like to hear
from some other packagers, and see what is easiest for them.
 This is essentially adding a step for packagers, which
certainly is no big deal.

So now we have txt, html, and pdf. Do we want to have a zip
archive for each? One big zip file? Should it be public, or
just there for packagers? 

----------------------------------------------------------------------

Comment By: Andreas Oesterhelt (oes)
Date: 2003-03-29 10:34

Message:
Logged In: YES 
user_id=78811

The PDF docs in CVS are very old. Keeping genereated stuff
in CVS
does suck big time, but there needs to be a way to build
packages
without jade, docbook & tools available. 

How about this:
Whoever does the release must, after freezing, but before src
package upload, update the docs on the webserver, incl.
text, pdf,
README etc. The package build targets then suck the docs from
privoxy.org.

We delete generated docs from CVS once and for all.

Any objections / ideas?

----------------------------------------------------------------------

Comment By: David Schmidt (david__schmidt)
Date: 2003-03-29 08:23

Message:
Logged In: YES 
user_id=249980

Looks like bad .pdfs made it into the OS/2 package.  The
soonest I can rebuild it is Monday.

- David

----------------------------------------------------------------------

Comment By: David Mediavilla (davidme)
Date: 2003-03-28 22:50

Message:
Logged In: YES 
user_id=595264

The PDFs from the .zip at privoxy.org work OK.

The ones I listed are those present in
privoxyos2_setup_3.0.2.exe.

So it seems that corrupt files were shipped.

----------------------------------------------------------------------

Comment By: Hal Burgiss (hal9)
Date: 2003-03-28 21:57

Message:
Logged In: YES 
user_id=322640

PS -- Those timestamps look like 3.0.0 time frame. Are they
accurate?

----------------------------------------------------------------------

Comment By: Hal Burgiss (hal9)
Date: 2003-03-28 21:38

Message:
Logged In: YES 
user_id=322640

David, thanks!

Unfortunately, I downloaded the 3.0.2 PDF docs from the
website, and they are all readable with Acrobat, Ghostview,
and xpdf  on Linux, with no problems.

Soooo....I am guessing we have a corruption problem in the
OS/2 packaging process or some other platform specific
issue. Can you try the ones posted on http://privoxy.org
(assuming you are talking about different ones, of course)? TIA.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=111118&aid=711668&group_id=11118