OpenSystemsDevelopment / qpdf

Commit ede1255a82665dd870451ac896bcef95a7830b57

Authored by Jay Berkenbilt
1 parent 7f889252

Update TODO

Inline Side-by-side
Showing 1 changed file with 5 additions and 26 deletions
... ... @@ -52,8 +52,11 @@ Small, command-line tool only enhancements to do soon
52 52 (libtool).
53 53  
54 54  
55   -6.1.0
56   -=====
  55 +Soon
  56 +====
  57 +
  58 + * Eliminate dependency on PCRE. There aren't that many regular
  59 + expressions, and they are used only for internal purposes.
57 60  
58 61 * Add method to push inheritable resources to a single page by
59 62 walking up and copying without overwrite. Above logic will also be
... ... @@ -65,10 +68,6 @@ Small, command-line tool only enhancements to do soon
65 68 * Provide an option for QPDFWriter to preserve unreferenced objects
66 69 when writing out a file.
67 70  
68   - * Look at all the exceptions and error conditions in QPDF_stream and
69   - figure out which ones should be converted to warnings and treating
70   - the stream as not filterable.
71   -
72 71 * Support user-pluggable stream filters. This would enable external
73 72 code to provide interpretation for filters that are missing from
74 73 qpdf. Make it possible for user-provided fitlers to override
... ... @@ -89,29 +88,9 @@ Small, command-line tool only enhancements to do soon
89 88 - Files that have no whitespace token after "endobj" such that
90 89 endobj collides with the start of the next object
91 90  
92   - - Files with individual corrupted streams. Just leave the streams
93   - unfiltered after giving a warning, or maybe do something else
94   - like applying as many of the filters as possible, etc.
95   - QPDFWriter can have some kind of retry mechanism on streams
96   - where filtering fails after filterable returns true.
97   -
98   - - Files whose PDF header is malformed, perhaps with no version
99   - number (as literally %PDF-a.b). Maybe keep track of features to
100   - try to infer a version based on encryption formats and object
101   - streams.
102   -
103   - - For really hard errors like corrupted streams where there is
104   - virtually guaranteed to be loss, maybe require an additional
105   - option to tell qpdf that it's okay to continue and treat those
106   - as warnings. Probably need separate options for each type of
107   - error plus a generic tryReallyHard kind of method that enables
108   - them all. Then the qpdf command-line tool can have a single
109   - flag that enables all supported aggressive recovery techniques.
110   -
111 91 - See ../misc/broken-files
112 92  
113 93  
114   -
115 94 General
116 95 =======
117 96  
... ...