summaryrefslogtreecommitdiffstats
path: root/TODO
diff options
context:
space:
mode:
authorJay Berkenbilt <ejb@ql.org>2012-12-31 15:27:02 +0100
committerJay Berkenbilt <ejb@ql.org>2012-12-31 16:32:32 +0100
commit06c5bac96c9d18d8336a65e2ad6f8283530514c2 (patch)
tree86d686a0e42715e5a18983c5989c8361b0ac6ecc /TODO
parentf8306913ba6eb751cd7f408d04f2d65d8cd3b341 (diff)
downloadqpdf-06c5bac96c9d18d8336a65e2ad6f8283530514c2.tar.zst
Clarify TODO note about crypt filters
Diffstat (limited to 'TODO')
-rw-r--r--TODO15
1 files changed, 8 insertions, 7 deletions
diff --git a/TODO b/TODO
index 7c5ea6b5..582e3ad9 100644
--- a/TODO
+++ b/TODO
@@ -79,13 +79,14 @@ Index: QPDFWriter.cc
* The description of Crypt filters is unclear with respect to how to
use them to override /StmF for specific streams. I'm not sure
whether qpdf will do the right thing for any specific individual
- streams that might have crypt filters. The specification seems to
- imply that only embedded file streams and metadata streams can have
- crypt filters, and there are already special cases in the code to
- handle those. Most likely, it won't be a problem, but someday
- someone may find a file that qpdf doesn't work on because of crypt
- filters. There is an example in the spec of using a crypt filter
- on a metadata stream.
+ streams that might have crypt filters, but I believe it does based
+ on my testing of a limited subset. The specification seems to imply
+ that only embedded file streams and metadata streams can have crypt
+ filters, and there are already special cases in the code to handle
+ those. Most likely, it won't be a problem, but someday someone may
+ find a file that qpdf doesn't work on because of crypt filters.
+ There is an example in the spec of using a crypt filter on a
+ metadata stream.
For now, we notice /Crypt filters and decode parameters consistent
with the example in the PDF specification, and the right thing