OpenSystemsDevelopment / qpdf

Commit 9e01c8bd996a15934f58979f447bea359e857875

Authored by Jay Berkenbilt
1 parent 4d0cb21f

TODO

Inline Side-by-side
Showing 1 changed file with 9 additions and 3 deletions
... ... @@ -3,9 +3,6 @@ Soon
3 3  
4 4 * Set up OSS-Fuzz (Google). See starred email in qpdf label.
5 5  
6   - * Look at files from bug 268 (../misc/bugs/268), which cause an
7   - internal error when linearized.
8   -
9 6 * Update the docs for copyForeignObject and addPage to explain the
10 7 difference between copying a page in the two ways: using addPage
11 8 updates the pages tree, while using copyForeignObject does not. The
... ... @@ -29,6 +26,9 @@ Do these things next time we have to break binary compatibility
29 26 * Rename QUtil::strcasecmp since strcasecmp is a macro on some
30 27 platforms. See #242.
31 28  
  29 + * Collapse QPDF::pushInheritedAttributesToPageInternal* and
  30 + QPDF::getAllPagesInternal* into QPDF::*Internal.
  31 +
32 32 Lexical
33 33 =======
34 34  
... ... @@ -107,6 +107,12 @@ things sent to me by email that are specifically not public. Even so,
107 107 I find it useful to make reference to them in this list
108 108  
109 109 * Do something better for inline images (see #278)
  110 + * Figure out a way to add an expectInlineImage method that takes
  111 + the offset of the EI image so an external system can locate the
  112 + end tag. Hopefully Both QPDFObjectHandle and Pl_QPDFTokenizer can
  113 + do this. Somewhere we might want something that uses an input
  114 + source to do it, but for the pipeline, it will also have to be
  115 + possible to do it as we go.
110 116 * Improve location of EI to handle EI embedded in the image data;
111 117 consider trying to parse after EI and, if errors, keep looking.
112 118 Will have to look at what happens with random binary characters
... ...