OpenSystemsDevelopment / qpdf

Commit 77e2b6e34eba28b3ad5b7158a954b5ae12946a8e

Authored by Jay Berkenbilt
1 parent 71566a27

Note about incremental updates

Inline Side-by-side
Showing 1 changed file with 9 additions and 3 deletions
... ... @@ -42,6 +42,11 @@ Next
42 42 stringify a JSON blob
43 43 * One option might be to prepend file:// to a filename or otherwise to take a JSON blob. We could
44 44 have that as a particular type of argument that would behave properly for both job JSON and CLI.
  45 +* Support digital signatures. This probably requires support for incremental updates. See
  46 + "incremental updates" in rejected ideas. That description is out of date but would need to be
  47 + cleaned up. See also issue #22.
  48 + * Make it possible to see incremental updates in qdf mode.
  49 + * Make it possible to add incremental updates.
45 50  
46 51 Possible future JSON enhancements
47 52 =================================
... ... @@ -561,9 +566,10 @@ Rejected Ideas
561 566  
562 567 * Investigate whether there is a way to automate the memory checker tests for Windows.
563 568  
564   -* Provide support in QPDFWriter for writing incremental updates. Provide support in qpdf for
565   - preserving incremental updates. The goal should be that QDF mode should be fully functional for
566   - files with incremental updates including fix_qdf.
  569 +* (This idea may be revised with alterations. Some of this is out of date.) Provide support in
  570 + QPDFWriter for writing incremental updates. Provide support in qpdf for preserving incremental
  571 + updates. The goal should be that QDF mode should be fully functional for files with incremental
  572 + updates including fix_qdf.
567 573  
568 574 Note that there's nothing that says an indirect object in one update can't refer to an object that
569 575 doesn't appear until a later update. This means that QPDF has to treat indirect null objects
... ...