Re: Is acroread blind, or ps2pdf dangerous?
On 2010-05-13 17:04 +0200, Merciadri Luca wrote:
> When compiling any .tex document using the route latex -> dvips ->
> ps2pdf, I get a PDF.
This is a rather clumsy way these days. Why don't you use pdflatex?
> Normal, but the problem is that if I the PDF is
> already opened (e.g. because I was reading the version of the document
> before having modified and compiled it) when the compilation and the
> whole process ends, the opened PDF is blank, i.e. the current page
> becomes white, and every page I go at is white.
The changes in the file seem to confuse acroread. At least it does not
crash.
> If I then re-open the
> document, I find the new version of my PDF.
A smart reader would have an option to detect changes to the file and
reload it automatically. Since I haven't used acroread for ages I don't
know whether it has such an option.
> I would like to know how this process actually works. For me, it looks
> like the ps2pdf tool creates the PDF from scratch, and overwrites the
> old PDF.
A quick experiment shows that this does not seem to be the case, ps2pdf
writes to the existing file.
> But why am I receiving no warning message from acroread?
Ask Adobe…
> Anyway, acroread seems not to be locking the file, or, if so, ps2pdf
> forces the writing.
I would be rather annoyed if a reader locked a file that it does not
even open for writing.
Sven
Reply to: