arlington-pdf-model

arlington-pdf-model copied to clipboard

ArrayOfStructElem can't contain null

13

Current definition of `ArrayofStructElem` specifies element types as `dictionary`, while it can also be `null`. See https://github.com/veraPDF/veraPDF-library/issues/1355

bdoubrov

Resources entry in Form XObject is only strongly recommended, not required

6

PDF 2.0 (Table 93) says that Resources entry in Type1 Form dictionary is _Optional but strongly recommended_, while the XObjectFormType1.tsv says it is required.

bdoubrov

Invalid special case for Di in Transition

7

Special case for Di in Transition is currently `fn:Eval((((@Di==90) || (@Di==180)) && (@S==Wipe)) || ((@Di==315) && (@S==Glitter)))` Possible values for entry Di: 0,90,180,270,315. If Di have value 0 or 270,...

MaximPlusov

Since each PDF library seems to have its own set of nuances, having a wider choice might show up further PDF file malformations and non-compliances, or even allow for additional...

petervwyatt

Extend the Arlington PDF model for content stream operators and operands

3

Extend the Arlington PDF model for content stream operators and operands, according to ISO 32000-2:2020. Things to check for: * correct number, type and range of operands for each operator...

petervwyatt

AS is always required in Widget annotations

5

`AnnotWidget.tsv` currently specifies that the **AS** entry is required if `fn:IsRequired(fn:IsPresent(AP::N::*) || fn:IsPresent(AP::R::*) || fn:IsPresent(AP::D::*))`. This corresponds to the following phrase from PDF spec: **AS** is _"Required if the appearance...

bdoubrov

Fields and Widgets, Widgets and Fields.

6

It was inevitable this was going to come up at some point. First, I'm assuming a processing model which means a node in the PDF can be of more than...

faceless2

Feature request: extend Arlington to have FDF rules as per clause 12.7.8. This might be possible using a new predicate e.g. `fn:isFDF()` which then alters `fn:IsRequired`, etc. in some way......

petervwyatt

When running the attached PDF file through `TestGrammar`, I get the error message > Error: wrong value for possible values: Subtype (FontFile3CIDType0) should be: name [CIDFontType0C] in PDF 1.7 and...

seehuhn

Due to TestGrammar PoC needing to do dictionary key normalization (via key sorting, so that all PDF libraries process keys in the same order so output is deterministic and independent...

petervwyatt