If I change every instance beginStream in backend_pdf.py to use None
rather than a reserved object for the length of the stream then
acroread/gv can process the resulting pdf files.
I'm guessing this will be less efficient for the writer since it has
to keep the entire stream in memory in order to compute its length
prior to writing it. The alternative would be to reserve space,
write the stream, rewind to write the length then seek forward to
the end, but that won't work if e.g., the pdf is sent to a pipe.
Let me know if I should post the changes.
- Paul
···
On Tue, Sep 11, 2007 at 10:57:18AM -0400, Paul Kienzle wrote:
I'm not sure yet how to fix the problem, but in the sample I sent
earlier if I change:
5 0 obj
<< /Length 11 0 R >>
endobj
to
5 0 obj
<< /Length 1239 >>
endobj
then both gv and acroread can process the file without error.
- Paul
Did r3829 not work for you? (Or did you miss that in my earlier post?)
I don't think anything related to Lengths has changed recently, and it did work at one point...
Cheers,
Mike
Paul Kienzle wrote:
···
On Tue, Sep 11, 2007 at 10:57:18AM -0400, Paul Kienzle wrote:
I'm not sure yet how to fix the problem, but in the sample I sent
earlier if I change:
5 0 obj
<< /Length 11 0 R >>
endobj
to
5 0 obj
<< /Length 1239 >>
endobj
then both gv and acroread can process the file without error.
- Paul
If I change every instance beginStream in backend_pdf.py to use None rather than a reserved object for the length of the stream then acroread/gv can process the resulting pdf files.
I'm guessing this will be less efficient for the writer since it has
to keep the entire stream in memory in order to compute its length
prior to writing it. The alternative would be to reserve space,
write the stream, rewind to write the length then seek forward to
the end, but that won't work if e.g., the pdf is sent to a pipe.
Let me know if I should post the changes.
- Paul
--
Michael Droettboom
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA