OpenSystemsDevelopment / qpdf

Commit d81ff5aa3d48d512b2579edc761b8094639694a2

Authored by Jay Berkenbilt
1 parent a70fbaaf

TODO

Inline Side-by-side
Showing 1 changed file with 18 additions and 2 deletions
@@ -4,7 +4,17 @@ Soon @@ -4,7 +4,17 @@ Soon
4 * Set up OSS-Fuzz (Google). See starred email in qpdf label. 4 * Set up OSS-Fuzz (Google). See starred email in qpdf label.
5 5
6 * Issue #219, not requiring QPDF reference of copied object to be 6 * Issue #219, not requiring QPDF reference of copied object to be
7 - kept around. Comments are in the issue. 7 + kept around. Comments are in the issue. Most likely we should take
  8 + all the encryption parameters and push them into a separate class
  9 + within QPDF. We can convert the encryption computation methods to
  10 + methods of that class and then hang onto that along with the input
  11 + stream for foreign streams. That should handle the encrypted file
  12 + case. For the stream data provider case, we don't have to do
  13 + anything special. In that case, it's definitely up to the user
  14 + to make sure the stream data provider and everything it uses stay
  15 + in scope. The user can use a PointerHolder<QPDF> if they want as
  16 + long as the original QPDF object is allocated this way. That would
  17 + be a good case for the test suite.
8 18
9 * Figure out how to render Gajić correctly in the PDF version of the 19 * Figure out how to render Gajić correctly in the PDF version of the
10 qpdf manual. 20 qpdf manual.
@@ -136,7 +146,13 @@ I find it useful to make reference to them in this list @@ -136,7 +146,13 @@ I find it useful to make reference to them in this list
136 146
137 * Pl_TIFFPredictor is pretty slow. 147 * Pl_TIFFPredictor is pretty slow.
138 148
139 - * Some test cases on bad fails fail because qpdf is unable to find 149 + * If we ever wanted to do anything more with character encoding, see
  150 + ../misc/character-encoding/, which includes machine-readable dump
  151 + of table D.2 in the ISO-32000 PDF spec. This shows the mapping
  152 + between Unicode, StandardEncoding, WinAnsiEncoding,
  153 + MacRomanEncoding, and PDFDocEncoding.
  154 +
  155 + * Some test cases on bad files fail because qpdf is unable to find
140 the root dictionary when it fails to read the trailer. Recovery 156 the root dictionary when it fails to read the trailer. Recovery
141 could find the root dictionary and even the info dictionary in 157 could find the root dictionary and even the info dictionary in
142 other ways. In particular, issue-202.pdf can be opened by evince, 158 other ways. In particular, issue-202.pdf can be opened by evince,