DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=42845>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=42845





------- Additional Comments From [EMAIL PROTECTED]  2008-01-16 00:24 -------
(In reply to comment #8)
<snip/>
> Is it possible that on a slow machine, the pdf file is not completely written 
> (buffer not completely emptied) while the FOP process signals the system it 
> is 
> ready and now acrobat opens a file where e.g. some crucial font information 
> at 
> the end of the file is not available, yet? When you open the file a second 
> time 
> the file is complete and therefore one can print it...
<snip/> 

That would mean that the aShell.Run command returns before the Java process has
completely finished. At any rate, the output file is properly finalized and
closed by FOP (I've checked). So, no, I can't imagine that there are still any
open buffers or something like that around (except in a faulty operating system
which would be a catastrophe and not affect only one program). Furthermore,
Acrobat usually notifies me if I want to open a PDF that is incomplete/corrupt.
I still believe in a bug in Acrobat but I could be wrong. Have you tried a
different PDF viewer? I know using Acrobat could be company policy but just in
order to narrow down the problem such an experiment could be worthwhile.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Reply via email to