Adobe Community : All Content - All Communities

Duplicate entries in the Fields array

forums_noreply@adobe.com — Mon, 25 Aug 2014 11:16:47 GMT

I came across a (strange) pdf and after an analysis it turned out that some of the fields occur multiple times in the Fields array.

Now when looking up the spec it states:

"An array of references to the document’s root fields (those with no ancestors in the field hierarchy)."

Is that a violation of the spec (although it doesn't state that explicitly)?

So how to deal with this kind of PDFs?

Appearance state (AS) vs. value (V) of Button Form Fields

forums_noreply@adobe.com — Thu, 31 Oct 2013 15:58:43 GMT

It all started with a PDF where the state of the checkboxes was visually different from our viewer to the acrobat reader.

After some investigation the problem was a different state of the /V and the /AS attributes:

...

/FT/Btn

/Subtype/Widget

/T(Checkbox1)

/V (0)

/AP <</N <</Off 20 0 R /0 21 0 R>>>>

/AS/Off

...

So the value states that the checkbox is checked and the appearance state says it is not checked.

I looked up the PDF spec it says:

V=value

(page 440) The V entry in the field dictionary (see Table 220) holds a name object representing the check box’s appearance state, which shall be used to select the appropriate appearance from the appearance dictionary.

AS=appearance state

(page 383) (Required if the appearance dictionary AP contains one or more subdictionaries; PDF 1.2) The annotation’s appearance state, which selects the applicable appearance stream from an appearance subdictionary (see Section 12.5.5, “Appearance Streams”).

Our viewer analyzed the content (/V) and the adobe reader obviously considered the appearance state (/AS).

If both are set and are different which one 'wins'?

From my perspective it is in violation of the spec that both are different. However

1.) since /V is optional and /AS is required one can argue that /AS has a slight "advantage" so to speak

2.) Also PDF/A-1 states that: "Every form field shall have an appearance dictionary associated with the field's data. A conforming reader shall render the field according to the appearance dictionary without regard to the form data." Which would also indicate in case of doubt look at the AS.

It would be nice if anyone can share his thoughts about it...

Outdated information about CDS

forums_noreply@adobe.com — Fri, 11 Oct 2013 12:11:41 GMT

I have a question regarding the CDS program - if I misplaced it please relocate the thread. Thanks.

All information I could find is here:

http://www.adobe.com/misc/pki/cds_cp.html

However,

1. The file is outdated. There is at least a version #15 from 2007 (or maybe even a newer one)

2. The list of partners able to provide a CDS ID is from 2005 and quite outdated. (Have a look in the reader there is a list of nearly 30 providers)

So where can I get the latest CDS Cerificate Policy document and a list of all current providers?

Thank!

Can't save/export file attachment

forums_noreply@adobe.com — Mon, 23 Sep 2013 09:43:12 GMT

I have a PDF file which contains a certificat (*.crt) file as an attachment.

However I am not able to save the certificate on the local file system. The following error message pops up:

"you have selected a file that cannot be exported from acrobat" The error occurs in Acrobat or in Adobe Reader (11.X)

I know that there are registry settings to reenable the saving (cDefaultLaunchAttachmentPerms) however that is no solution for (external) client pcs...

What I now don't understand is - the parameter is called 'cDefaultLaunchAttachmentPerms' which contains Launch - so if I open it (via Launch/Open Attachment) that should be forbidden and however not the 'Save Attachment' option...?

Is that a bug? (If not the option should be renamed) But how do I then get the file out?

PDF form field rectangle out of page coordinates

forums_noreply@adobe.com — Fri, 18 Jan 2013 16:02:33 GMT

Hi,

recently i came across a PDF file which had a (text) form field with the following rectangle coordinates:

LowerLeft: 170;850

UpperRight: 475;862

The page itself had: 595;841 whereas MediaBox=CropBox=BleedBox=TrimBox.

Thus the y coordinate is out of the page so to speak.

The adobe reader displays the field at the upper top of the page but within the boundaries of the page.

Maybe it does correct/fix it?

My question is:

1.) Is that pdf spec compliant? (I did a quick search however couldn't find anything about it)

2.) Is that PDF/A-1 compliant (if that makes a difference)?

Thanks,

ToM

same dictionary for document info dictionary and Page Tree

forums_noreply@adobe.com — Mon, 10 Dec 2012 10:31:56 GMT

Hi,

recently i came across a pdf file which had the same dictionary for the info dictionary and the page tree.

Thus this "dictionary" looked like this:

5 0 obj

<</Author (author) /Count 1 /CreationDate (D:2011112617302401'00') /Creator() /Keywords (keywords) /Kids [8 0 R] /ModDate (D:2011112617302401'00') /Producer (producer) /Subject (subject) /Title (title) /Trapped /False /Type /Pages >>

Beside the (bad) readability aspect - is that spec compliant?

Thanks

ToM

Implication of the Lock dictionary

forums_noreply@adobe.com — Thu, 26 Apr 2012 13:32:40 GMT

Hi Forum, Hi Leonard :-)

I have a question regarding the Lock dictionary of a signature field.

Per definition it "[...] specifies a set of form fields that shall be locked when this signature field is signed."

1.)

Locking means that the annotation flag (F) at bit position 8=Locked of a formfield is set?

2.)

Does it include to set the LockedContents, too?

Thanks,

ToM

Acrobat X - Win7 Problem: Access denied

forums_noreply@adobe.com — Fri, 03 Dec 2010 10:45:23 GMT

Hi,

since the new version X our plugin doesn't work anymore when using it with Win7. WinXP still works fine with version 10.X and version 9.X works fine with all OSs. We are using the following method:

AVDocPrintPagesWithParam(...)

and on Win7 systems an errorcode "Access Denied" is returned.

Anybody any idea? Any known bug?

Thanks

ToM

small error in pdf spec

forums_noreply@adobe.com — Tue, 11 Oct 2011 14:29:35 GMT

found a possible error in the pdf spec PDF 32000-1:2008:

page 385, Table 165 – Annotation flags

8 bit position - Locked (PDF 1.4)

In pdf 1.4 there was no flag 'locked' at the 8bit position.

(there are also lots of spelling mistakes but don't want to nit-pick ;-)

Reader X: ProtectedModeWhitelistConfig.txt entry results in error

forums_noreply@adobe.com — Thu, 22 Sep 2011 16:18:25 GMT

Hi,

to make a plugin work again in the Reader X 10.1.1 i added a policy file.

Nearly everything is working however i can't use the 'REG_ALLOW_ANY' key.

The logging output is e.g.:

<snip>

[09:22/16:23:40] NtCreateKey: STATUS_ACCESS_DENIED

[09:22/16:23:40] real path: \REGISTRY\MACHINE\Software\Adobe

[09:22/16:23:40] Consider modifying policy using this policy rule: REG_ALLOW_ANY

[09:22/16:23:40] NtCreateKey: STATUS_ACCESS_DENIED

[09:22/16:23:40] real path: \REGISTRY\MACHINE\SOFTWARE\Adobe

[09:22/16:23:40] Consider modifying policy using this policy rule: REG_ALLOW_ANY

<snip>

-> I tried the following keys however always get an 'Custom policy syntax error' :

REG_ALLOW_ANY= \REGISTRY\MACHINE\Software\Adobe*

REG_ALLOW_ANY= \REGISTRY\MACHINE\Software\Adobe**

REG_ALLOW_ANY=HKEY_CURRENT_USER\SOFTWARE\Adobe*

REG_ALLOW_ANY=HKEY_LOCAL_MACHINE\SOFTWARE\Adobe*

Any ideas?

Thanks

ProtectedModeWhitelistConfig.txt entry results in error

forums_noreply@adobe.com — Fri, 23 Sep 2011 08:29:49 GMT

Hi,

to make a plugin work again in version 10.1.1 i added a policy file.

Nearly everything is working however i can't use the 'REG_ALLOW_ANY' key.

The logging output is e.g.:

<snip>

[09:22/16:23:40] NtCreateKey: STATUS_ACCESS_DENIED

[09:22/16:23:40] real path: \REGISTRY\MACHINE\Software\Adobe

[09:22/16:23:40] Consider modifying policy using this policy rule: REG_ALLOW_ANY

[09:22/16:23:40] NtCreateKey: STATUS_ACCESS_DENIED

[09:22/16:23:40] real path: \REGISTRY\MACHINE\SOFTWARE\Adobe

[09:22/16:23:40] Consider modifying policy using this policy rule: REG_ALLOW_ANY

<snip>

-> I tried the following keys however always get an 'Custom policy syntax error' :

REG_ALLOW_ANY= \REGISTRY\MACHINE\Software\Adobe*

REG_ALLOW_ANY= \REGISTRY\MACHINE\Software\Adobe**

REG_ALLOW_ANY=HKEY_CURRENT_USER\SOFTWARE\Adobe*

REG_ALLOW_ANY=HKEY_LOCAL_MACHINE\SOFTWARE\Adobe*

Any ideas? What am i doing wrong?

Thanks

Valid checkbox state?

forums_noreply@adobe.com — Tue, 24 May 2011 11:23:27 GMT

Hi,

just got a PDF in my hands which uses the following syntax for its checkbox form fields:

/Rect[334.917 217.154 352.917 235.154]

/Subtype/Widget

/F 4

/P 1 0 R

/T(checkbox_name)

/V/

/FT/Btn

/Type/Annot

/MK<</BG[1.0]/CA(8)/BC[0.0]>>

/AP<</D<</ 83 0 R/Off 88 0 R>> /N<</ 97 0 R/Off 62 0 R>>>>

/AS/>>

Is it valid to have an empty appeareance state name "/" (cp. /V /D and /AS key)?

Shouldn't it have at least one letter?

I looked up the spec but couldn't find the definition for the name...

Any help appreciated,

ToM

PDF (name) Registry

forums_noreply@adobe.com — Mon, 26 Jul 2010 10:25:29 GMT

Hi,

i have a question regarding the PDF name registry. In the form (http://www.adobe.com/devnet/acrobat/pdfs/pdfregistry_v3.pdf) it says:

The registry will be publicly available.

So where is that? So how can i download or get the registry?

Lets say i have sucessfully registered a 2nd class pdf name (prefix) and i am using it to add one more attribute to a text form field.

Is there anyway to add my own (officially) prefixed attribute with acrobat (e.g. with java script or something like that)?

Just out of curiosity: Is the prefix case sensitive?

Thanks,

ToM

Differences for 'V' and 'DV' of a signature field

forums_noreply@adobe.com — Wed, 21 Jul 2010 16:17:16 GMT

I have a questions regarding the signature dictionary (PDF 1.4 since PDF/A).

According to the spec V and DV entries of a field dictionary (of a signature field) both contain signature dictionaries.

According to the signature dictionary spec the following attributes are required:

- Filter

- ByteRange

- Contents

-> If i add an V entry those attributes have to be filled (at the time of signing the document)

But what about the DV entry?

Quote from the spec:

"The DV (default value) entry in the field dictionary may specify a signature dictionary for an unsigned field that is preloaded with default values for some
entries."

-> Thus i don't need to prefill those upper three? At the time of the prefilling one can't fill those three because the information is not available...

Thanks for helping,

ToM

Problem with Fonts (DR, DA)

forums_noreply@adobe.com — Thu, 10 Jun 2010 11:53:58 GMT

My last question was regarding the usage of the DR attribute, which should be defined in the interactive form dictionary.

I did that but still different readers or the acrobat seem to have problems with the PDFs...

I definined Fonts as part of the interactive form dictionary:

/DR<</Font<</Times#20New#20Roman 11 0 R >>>>

In a textfield i referenced that font in a /DA:

/DA(/Times#20New#20Roman 0 Tf 0 g)

The #20 is allowed i was told (its a replacement of a blank).

Besides strange visual behaviour in acrobat 8.1 after i save the document acrobat uses helvetica for the field, as if it couldn't find the font...?

Strange thing ;-)

Thanks for helping,

ToM

DR and DA

forums_noreply@adobe.com — Tue, 18 May 2010 16:53:40 GMT

I have a question regarding the DR attribute (PDF/A Spec):

In the interactive form dictionary the DR attribute is defined as:

"A document-wide default value for the DR attribute of variable text fields"

and then the DR attribute can be used again in the field dictionary (containing variable text):

"(Required; inheritable) A resource dictionary containing default resources (such as fonts ...)

to be used by the appearance stream. At a minimum, this dictionary must contain a Font entry
specifying the resource name and font dictionary of the default font for displaying the
field’s text."

So as I see it I can (=optionally) define a "global" DR attribute which is valid for all (textual) fields.

And secondly I must (=required) define a DR attribute on a per field basis.

1. Is that so?

2. What's in case if a global DR is defined can't i "skip" the per-field DRs?

3. Is it possible to define only one DR (global or per-field?)

4. Which takes the "lead" if both are specified?

Thanks,

ToM

BaseFont and FontName must be equals?

forums_noreply@adobe.com — Thu, 06 May 2010 14:01:28 GMT

I have trouble with an PDF/A document and some readers we are using:

- Acrobat (Reader) 9.X works fine

- Acrobat (Reader) 6.X and our own inhouse reader have problems

I tracked it down to the following part:

10 0 obj
<</LastChar 255/BaseFont/TimesNewRomanPSMT/Type/Font/Encoding/WinAnsiEncoding/Subtype/TrueType/FirstChar 0/FontDescriptor 11 0 R/Widths[...<removed the numers in here>...]>>
endobj

11 0 obj

<</CapHeight 666/FontBBox[-1164 -628 4096 2062]/Type/FontDescriptor/Descent -442/FontFile2 33 0 R/StemV 87/Flags 32/Ascent 1420/FontName/Times#20New#20Roman/ItalicAngle 0>>
endobj

The problem is the /FontName of the FontDescriptor contains "Times#20New#20Roman".

In the pdf spec i read:

BaseFont: "The PostScript name of the font. For Type 1 fonts, this is always the value of the FontName entry in the font program"

FontName: "The PostScript name of the font. This name shall be the same as the value of BaseFont in the font or CIDFont dictionary that refers to this font descriptor."

=> Thus the BaseFont and the FontName must have the same value?

=> Is that "#20" (= a blank?) even allowed inside the FontName?

Thanks for the help,

ToM

SubFilter value algorithm support in PDF/A

forums_noreply@adobe.com — Mon, 01 Mar 2010 14:41:42 GMT

Hi Leonard (since you answer most of the questions anyway )

i have a question regarding the use of a stronger hash or encryption strength in a PDF/A document. In one of your previous posts you stated:

"For example, for true PDF/A-1 compatibility you should not use SHA256 since it didn't exist in PDF 1.4 (on which PDF/A-1 is based) even though it would be a perfectly valid PDF file."

Now i read another document of yours called 'ISO 19005-1 (PDF/A-1) Application Notes'. There on page 30 'Digital Signatures' you write:

"Revocation: As with Timestamping, since the presence of certificate revocation information does not effect the visual display of the PDF, it is permitted by PDF/A-1, even though it is a PDF 1.5 feature."

Now one could say that using a stronger hash or encryption algorithm falls into the same category:

So for instance even if RSA 2048 and SHA256 were not supported in 1.4 (but in 1.5) - shouldn't they be permitted in PDF/A also?

Isn't that, although not explicitly mentioned, well within the stated goals of PDF/A-1?

Thanks

ToM

catalog dictionary: /AcroForm optional or required

forums_noreply@adobe.com — Thu, 07 Jan 2010 16:13:28 GMT

Hi,

i have a question:

PDF 1.4 (due to PDF/A) specification defines the 'AcroForm' key in the catalog dictionary as optional.

But this can mean two things:

- If the pdf has form NO fields -> optional

- If the pdf has form fields -> required

- If the pdf has form NO fields -> optional

- If the pdf has form fields -> optional

So can the key be omitted even if a document has form fields?

Thanks

ToM

Signature Dictionary 'Filter'

forums_noreply@adobe.com — Wed, 16 Dec 2009 09:37:00 GMT

I have a question about the 'filter' in the signature dictionary. It is defined as (taken from PDF 1.4 due to PDF/A):

Filter name (Required; inheritable) The name of the signature handler to be used for authenticating the field’s contents, such as Adobe.PPKLite, Entrust.PPKEF, CICI.SignIt, or VeriSign.PPKVS.

1.) A plugin is used to validate signatures, right? (please correct me if i am wrong here)

2.) Can the subfilter (like adbe.pkcs7.detached or adbe.pkcs7.sha1) also be used with other filters than adobe.ppklite?

2) The Adobe.PPKLite is the "default" plugin? (which every reader since 5.0 or so has)

3.) The other handlers are also part of acrobat? (such as entrust, verisign etc.)

4.) What must i do to register my own handler?

5.) What would happen if one would set the filter which is not existent?

Thanks for clarification,

ToM

PDF 1.4 - order of form fields (tab order, signing order)

forums_noreply@adobe.com — Wed, 25 Nov 2009 17:44:16 GMT

I have a question related the order of form fields:

How can I influence the order of fields?

I use signature fields and want to explicitly set which signature is signed first, second etc.

Also the tab order would be interesting. (For that since PDF 1.5 there is a 'Tabs' key however how is that done in PDF 1.4?)

Any help appreciated,

Regards,

ToM

Digital signature Filter / SubFilter

forums_noreply@adobe.com — Wed, 25 Nov 2009 13:06:08 GMT

Hi,

i have a question regarding the use of digital signatures.

As a filter value i am usingPDF32000.bookAdobe.PPKLite but i am not quite sure about the SubFilter. As i understand there are three possible values:

PDF32000.book- adbe.pkcs7.detached
- adbe.pkcs7.sha1
- adbe.x509.rsa.sha1

Now i need to create PDF/A compliant pdfs and i read somewhere that it is not recommended (or not compliant?) to use

'adbe.x509.rsa.sha1' (pkcs#1 format). Instead one of the other two should be used.

Now since SHA1 is too weak only 'adbe.pkcs7.detached' (pkcs#7 format) remains.

But what does the 'detached' stands for?

Does it mean that the digest or the certicate have to be stored in an extra file? (Similar to the xml signing mechanism: "Enveloping signatures are over data within the same XML document as the signature; detached signatures are over data external to the signature element.") ?

Thanks for clarifying,

ToM

PDF/A vs. Form Fields (checkboxes, radiobuttons)

forums_noreply@adobe.com — Fri, 16 Oct 2009 15:25:32 GMT

I've question regarding the PDF/A specification and would appreciate some clarification.

The specs says:

"If an annotation dictionary contains the AP key, the appearance dictionary that it defines as its value shall contain only the N key, whose value shall be a stream defining the appearance of the annotation. [...] Every form field shall have an appearance dictionary associated with the field's data. A conforming reader shall render the field according to the appearance dictionary without regard to the form data."

Now i have a document which is fully PDF/A compliant however the acrobat preflight (8 & 9) check fails with the message that my checkboxes do not only contain the /N key. However they do contain just the /N (normal) appearances.

1.) So what's the problem? (Can't think that this should be a bug since intarsys PDF/A validation also reports it...)

The PDF Spec 1.4 defines the 'normal' appearance of a checkbox like that:

/AP << /N << /On formXObject1 /Off formXObject2>>>>

2.) Or does the spec mean, that there can only be one appearance inside the /N enty?

Then PDF 1.4 states:

"The appearance for the off state is optional, but if present must be stored in the appearance dictionary under the name Off."

3.) So if i only define the "On" state the document will become fully PDF/A compliant?

4.) And what about the Appearance state (AS)? PDF 1.4 states:

"The choice between the checked and unchecked appearance states is determined by the AS entry in the annotation dictionary"

But PDF/A does not mention the /AS key but it is vital for checkboxes...?! According to the spec a viewer has to "render the field according to the appearance dictionary" -> but checkboxes can have two states ....

Thanks for bringing any light on this!

/ToM

Looking for "PDF Public-Key Digital Signature and Encryption Specification"

forums_noreply@adobe.com — Fri, 13 Feb 2009 09:29:56 GMT

Hi,

i am looking for the following ("old") document:

PDF Public-Key Digital Signature and Encryption Specification

Originally i could be found here:
http://partners.adobe.com/asn/developer/acrosdk/DOCS/ppk_pdfspec.pdf

But not anymore. Does somebody of you still have it? Adobe today just offers the latest documents but i specifically need that older version.
Or is there an archive i don't know of?

Thanks for your help,
ToM

Acrobat (8.1.2): How to add 'mapping name' (/TM)

forums_noreply@adobe.com — Mon, 29 Sep 2008 13:12:01 GMT

The PDF spec (1.4) defines that every form field can have an (optional) mapping name (key is TM). Is there a way to set this mapping name with Acrobat Profession 8.1.2?

Thanks for any help,
ToM

From the PDF spec 1.4 pp. 531:
(Optional; PDF 1.3) The mapping name to be used when exporting interactive
form field data from the document.