This Form Requires Adobe Acrobat Reader For Mac Or Windows
Most major publishers use Adobe Digital Editions (ADE) to proof-read their books. Download this free eReader to experience your books in the most optimum format across PC, MAC, tablets or mobile devices. Use it to download and purchase digital content, which can be read both online and offline. Print documents reliably from any Windows or Mac application by selecting Adobe PDF as your printer. Start your free trial to print to PDF using Adobe Acrobat DC. Print documents reliably from any Windows or Mac application by selecting Adobe PDF as your printer. Requires annual commitment. Team licenses available.
By December 1, 2009 Just about all PDF documents are intended to be viewed at some point in Reader. If a document includes scripts, and this is especially true for forms, then it must be tested in Reader.
Not all operations in will work in the Reader scripting environment, and some operations require Reader Rights Enabling in order to work. In this article, we’ll explore the various restrictions of Reader scripting and methods for testing and debugging code directly in the Reader environment. By the way, when you see the capitalized word 'Reader' in this article it means Adobe Reader. Reader script restrictions Reader is a much smaller and more restrictive tool than Acrobat Pro. Reader is free and intended for viewing PDF files, not creating and modifying PDF files like Acrobat. So in general, any operation that’s related to PDF creation and modification is not allowed.
To be more specific, Reader coding restrictions can be placed in 4 categories: • Operations that are completely forbidden. • Operations that are only possible if the PDF is Rights Enabled for that operation. • Operations that are version dependent. • Operations that require Privilege.
The uses a Rights (or Quick) Bar ( Figure 1) to indicate which restrictions apply to which functions and properties in the AcroForm model. The Rights Bar is a group of at least four boxes. Each box displays a specific restriction on the usage of a scripting operation. The Rights Bar is a mandatory reference when deciding whether or not an operation can be used in a particular scripting environment. Figure 1 – Each box in the Rights Bar indicates a specific usage restriction The Acroform Model is the oldest Document Object Model in Acrobat and the one used for scripting Acrobat forms and automation scripts.
Unfortunately, the documentation for the LiveCycle Scripting Model is not so clear when it comes to providing the same information. However, as a rule of thumb, only the functions and properties in the LiveCycle Host and SourceSet models have restrictions on them; everything else is open for use in Reader.
A little known secret is that the Host Model functions actually call the equivalent AcroForm functions. You can get an idea of how these functions are restricted by looking in the Acrobat JavaScript Reference. Let’s take a closer look at how these restrictions work by examining the Rights Bars for some common scripting functions. The Rights Bar shown in Figure 2 is for the most common function used in any PDF script.
The Doc.getField() function is used the acquire a Field Object. Figure 2 – No usage restrictions This function is an absolute necessity for any kind of form-field handling, so it’s important for it to work in Adobe Reader without any restrictions, which is exactly what the Rights Bar shows.
This Form Requires Adobe Acrobat Reader For Mac Or Windows Laptop
The first box indicates that getField() was first added to Acrobat/Reader in version 3.01. This is also the first version of Acrobat that contained JavaScript, so this function was one of the originals.
The following boxes are all empty, meaning there are no restrictions. This function will, for all practical purposes, work in all versions and variations of Acrobat, including Adobe Reader. Now let’s look at a heavily restricted operation, the Doc.insertPages() function ( Figure 3).
Figure 3 – Can only be used under special circumstances This function was added to Acrobat in version 5. Knowing the version an operation was added in is very important.
It is generally a bad idea to use operations added in the most recent versions of Acrobat, because many Reader users will still be at least one or two versions behind. It is also common for Adobe to add new features (function inputs) to an existing operation.