we are not editing the file - we are annotating it.
annotations are saved as separate objects (files) that are associated with the original. the original is never changed
how does a plugin switch off this behaviour so that we can set our own usage policies and address the needs of our customers?
Annotations are objects in a PDF – thus adding an annotation will CHANGE the PDF document.
Acrobat doesn't have a concept of "editable ONLY in memory" (which is what you are asking for).
There is no way to turn this off – it is engrained in the core libraries.
oh, ok. So what you are saying is that the core API will disable *any* write to the in-memory pdf if it is of pdf/a format.
Is this the same for the client plugin API and the livecycle server api? i believe that our livecycle server managed to assign reader-rights to the pdf/a document, which sounds like it shouldnt be able to do. Is that a bug?
It's doesn't disable the lowest level changes – but it does make the PDF appear as "read only" to higher level APIs (such as AddAnnot).
You can assign rights to a PDF/A, but it wouldn't matter since as long as it's PDF, it can't be commented on.. If you remove the PDF/A compliance, then it can.
Europe, Middle East and Africa