* Set tab order when document is tagged
* Update approach and add inverse test
* Revert page dictionary setup
* Update lib/mixins/markings.js
* Update kitchen-sink-accessible.pdf
* Update CHANGELOG.md
---------
Co-authored-by: Libor M. <liborm85@gmail.com>
* Add an option check to acroform mixin _resolveFlags().
This resolves#1495.
* Reworked fix to remove flags from options, if they are falsey.
* Added unit test for ignoring false flags in acroforms
* Added entry for removing false flags in changelog.
This makes the resulting PDF files smaller. It's cumbersome to filter out all commands that could result in identity transforms in code that's using PDFKit, so it makes sense to have the check in the transform() function.
* Added PDF/A-2 and PDF/A-3 subsets A and B
It seems like PDF/A-2 and PDF/A-3 are not very different from PDF/A-1 as far as the A and B subsets are concerned (A requires tagging which PDFKit supports already). With this change, we can let the generated PDF present itself as PDF/A-2 or PDF/A-3.
* Updated docs and changelog for new PDF/A subsets
* Fixed an issue where ICC profile path can be wrong for built package but good for tests
* pdf/a1b support initial commit
Added mixin for support pdf/a1b and a few of the things it requires (xmp metadata, colour profile). Currently, the CIDSet stream is the only error it comes back with the test case I'm using, will try sorting it out next.
* Adding CIDSet when generating PDF/A
PDF/A1 b/a requires a CIDSet. This is not checked by a validator and other converters seem to add a CIDSet with a value of FF FF FF FF 0C, so this commit does the same. When extending support for PDF/A 2/3/4, we may not add a CIDSet (I think for PDF/A3 it's not required?) or we will look for a proper way to generate the CIDSet.
At this point, PDFKit should be able to generate PDF/A1b which can pass veraPDF validation and PDF/A1a if tagged is enabled.
All you have to do is set pdfa: '1a' or pdfa: '1b' in the options passed to new PDFDocument.
* pdf/a intro docs
* generalising subsets, reimplementing pdfa1 and added control over metadata
added a generalised subsets mixin which can pull in a subset at runtime.
reimplemented pdfa1 mixin as some features should be standardised across all subsets, such as storing /Info as xmp metadata for pdf >1.3
added a metadata class and mixing to control and write the metadata to a pdf
* added tests for pdfa1 and metadata and moved joinTokens in helpers
Addeds tests for pdfa1 subset and metadata.
Moved joinTokens into helpers.js as it's now used in at least two places.
Added tests for document to when metadata should be added (pdf version 1.4 or newer) and when it shouldn't (pdf version 1.3)
* updated pdf/a docs to reflect latest changes
* store color profile as icc file
* Updated changelog to include PDF/A support in Unreleased section
* Rework integrations tests to compare pdf screenshots instead of raw content
* Update documentation and configuration related to integration/visual tests
Text options currently add a link annotation unless the link is `undefined` or `null`. When the text options are built using the continued flag any value that is `null` or `undefined` is overridden by the continued options. As `0` is used for a first page link, it should be allowed to specify `false` to stop continued text being a link.
Rename widgetAnnot method to widgetAnnotation
Rename initAcroForm method to initForms
Ensure existing unit tests pass.
Add formChoice example to test-acroform.js.
Minor documentation changes for forms.
