A way for software developers to add additional functionality to Acrobat or to modify current functionality.
Why are plug-ins required?
Adobe provides a product that is intended to be used across multiple industries and organisations. Supporting all multiple vertical markets bloats the application in proving features that would only be used by relatively few people when compared with the whole Acrobat market.
Can Acrobat plug-ins be used in the Adobe Reader?
Special support needs to be added to the plug-in so that it can run under Adobe Reader. However the Reader plug-in will require a special license and needs to go through an approval process with Adobe Systems Inc. - https://www.adobe.com/devnet/reader/ikla.html.
Are plug-ins specific to a particular version of Adobe Acrobat?
We have plug-ins that we developed for Acrobat 6 that still run without modification in Acrobat DC. However, if new features are used that are specific to a later version then it won't work under later versions. If earlier versions used the Adobe Dialog Manager (ADM) then they won't now work in current versions of Acrobat.
Examples of Plug-ins
- New security handlers that might be specific to a particular organisation. For example, we have developed security handlers that do not allow PDF files to be viewed outside a particular organisations offices.
- New annotations. For example, we created a plug-in that supported all of the British Standard Markups.
- Flattening annotations and form fields into the main document. This ensured that they could not be changed or modified and that they would print as part of the document even if the printing of annotations was switched off.
- Adding text and images to PDF files.
- Creating a table of Contents for PDF files
- Adding fields for variable data printing
- Hardware integration of Adobe Acrobat into whiteboards and interactive tables