diff options
author | Jay Berkenbilt <ejb@ql.org> | 2022-05-18 01:18:02 +0200 |
---|---|---|
committer | Jay Berkenbilt <ejb@ql.org> | 2022-05-20 15:16:25 +0200 |
commit | 0fe8d4476205c97e402e555aac41a88e70e3e9b2 (patch) | |
tree | 87c9ee190bdfe4deeb8c517a3da6ab6b2a2230eb /TODO | |
parent | 63c7eefe9db8d8e87d07198355627af01cc1814d (diff) | |
download | qpdf-0fe8d4476205c97e402e555aac41a88e70e3e9b2.tar.zst |
Support stream data -- not tested
There are no automated tests yet, but committing work so far in
preparation for some refactoring.
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 9 |
1 files changed, 7 insertions, 2 deletions
@@ -54,14 +54,14 @@ Soon: Break ground on "Document-level work" Output JSON v2 ============== -XXX - * Reread from perspective of update * Test all ignore cases with QTC * Test case of correct file with dict before data/datafile * Have a test case if possible that exercises the object description which means we need some kind of semantic error that gets caught after creation. +* Test invalid data, invalid data file +* Tests: round-trip through json, round-trip through qpdf --qdf Try to never flatten pages tree. Make sure we do something reasonable with pages tree repair. The problem is that if pages tree repair is @@ -236,6 +236,11 @@ Other documentation fodder: You can't create a PDF from v1 json because +* Change: names are written in canonical form with a leading slash + just as they are treated in the code. In v1, they were written in + PDF syntax in the json file. Example: /text#2fplain in pdf will be + written as /text/plain in json v2 and as /text#2fplain in json v1. + * The PDF version header is not recorded * Strings cannot be unambiguously encoded/decoded |