mirror of
https://github.com/qpdf/qpdf.git
synced 2025-01-03 15:17:29 +00:00
TODO notes
This commit is contained in:
parent
558590f0d0
commit
6a7c458381
26
TODO
26
TODO
@ -11,6 +11,7 @@ In order:
|
|||||||
|
|
||||||
Other (do in any order):
|
Other (do in any order):
|
||||||
|
|
||||||
|
* Good C API for json v2
|
||||||
* QPDFPagesTree -- avoid ever flattening the pages tree.
|
* QPDFPagesTree -- avoid ever flattening the pages tree.
|
||||||
* Check about runpath in the linux-bin distribution. I think the
|
* Check about runpath in the linux-bin distribution. I think the
|
||||||
appimage build specifically is setting the runpath, which is
|
appimage build specifically is setting the runpath, which is
|
||||||
@ -57,13 +58,30 @@ Output JSON v2
|
|||||||
|
|
||||||
Remaining work:
|
Remaining work:
|
||||||
|
|
||||||
* Make sure all the information from --check and other informational
|
* Make sure all the information from informational options is
|
||||||
options (--show-linearization, --show-encryption, --show-xref,
|
available in the json output.
|
||||||
--list-attachments, --show-npages) is available in the json output.
|
|
||||||
Consider having --check, --show-encryption, etc., just select the
|
* --check: add but maybe not by default?
|
||||||
|
|
||||||
|
* --show-linearization: add but maybe not by default? Also figure
|
||||||
|
out whether warnings reported for some of the PDF specs (1.7) are
|
||||||
|
qpdf problems. This may not be worth adding in the first
|
||||||
|
increment.
|
||||||
|
|
||||||
|
* --show-xref: add
|
||||||
|
|
||||||
|
* --encryption: show recovered user password when available
|
||||||
|
|
||||||
|
* --list-attachments: add information from --verbose. Add to a
|
||||||
|
"details" subkey.
|
||||||
|
|
||||||
|
* Consider having --check, --show-encryption, etc., just select the
|
||||||
right keys when in json mode. I don't think I want check on by
|
right keys when in json mode. I don't think I want check on by
|
||||||
default, so that might be different.
|
default, so that might be different.
|
||||||
|
|
||||||
|
* Consider having warnings be included in the json in a "warnings" key
|
||||||
|
in json mode.
|
||||||
|
|
||||||
Notes for documentation:
|
Notes for documentation:
|
||||||
|
|
||||||
* Find all mentions of json in the manual and update.
|
* Find all mentions of json in the manual and update.
|
||||||
|
Loading…
Reference in New Issue
Block a user