[cl-pdf-devel] Problem with write-document with stream as opposed to pathname
Erik Enge
erik at nittin.net
Thu Feb 26 20:52:10 UTC 2004
I get two substantially different documents if I call write-document
with a stream and a pathname.
Ignoring creation date differences, in the one where I passed a stream
to write-document, I observe
/CLF101 instead of /CLF104 (don't know if this matters).
But probably what makes my document generated via the stream unreadable
in Adobe Acrobat
Reader version 6.0 for Mac OS X is the following:
0 10 0 10
0000000000 65535 f 0000000000 65535 f
0000000009 00000 n 0000000NIL 00000 n
0000000059 00000 n 0000000NIL 00000 n
0000000145 00000 n 0000000NIL 00000 n
0000000205 00000 n 0000000NIL 00000 n
0000000223 00000 n 0000000NIL 00000 n
0000000472 00000 n 0000000NIL 00000 n
0000001952 00000 n 0000000NIL 00000 n
0000002050 00000 n 0000000NIL 00000 n
0000004364 00000 n 0000000NIL 00000 n
trailer trailer
<< /Size 10 << /Size 10
/Root 1 0 R/Info 2 0 R /Root 1 0 R/Info 2 0 R
>> >>
startxref startxref
4467 NIL
%%EOF %%EOF
The right is where I passed write-document a pathname, the left, a
stream.
Looking at the code in cl-pdf I don't see how this can happen so I'm
wondering if
I have aggravated something else, somewhere else. I am absolutely sure
that the
only thing I am changing to reproduce this (it is fully reproducible)
is whether I say
(pdf:write-document #p"/tmp/test.pdf")
or
(pdf:write-document *my-stream*)
Any clues? I'm running cl-pdf 2.0 in LW 4.3.0 on Mac OS X 10.3.2.
Erik.
More information about the cl-pdf-devel
mailing list