aboutsummaryrefslogtreecommitdiffstats
path: root/TODO
diff options
context:
space:
mode:
authorJay Berkenbilt <ejb@ql.org>2012-06-22 05:06:48 +0200
committerJay Berkenbilt <ejb@ql.org>2012-06-22 05:09:05 +0200
commita0768e419064b66ea6eb3e06a4398806b24311e8 (patch)
tree6ecfa1f080bdab2ee4573d14dd71c06507b84bdd /TODO
parent9eb8c9159b97b500e0ecb36271b663cafc89d932 (diff)
downloadqpdf-a0768e419064b66ea6eb3e06a4398806b24311e8.tar.zst
Add QPDF::emptyPDF() and pdf_from_scratch test code
Diffstat (limited to 'TODO')
-rw-r--r--TODO31
1 files changed, 29 insertions, 2 deletions
diff --git a/TODO b/TODO
index 6a20fa15..7f997b52 100644
--- a/TODO
+++ b/TODO
@@ -13,6 +13,35 @@ Next
- update README-windows.txt docs to indicate that MSVC 2010 is the
supported version and to update the information about mingw.
+ * Testing for files > 4GB
+
+ - Create a PDF from scratch. Each page has a page number as text
+ and an image. The image can be 5000x5000 pixels using 8-bit
+ gray scale. It will be divided into 10 stripes of 500 pixels
+ each. The left and right 500 pixels of each stripe will
+ alternate black and white. The remaining part of the image will
+ have white stripes indicating 1 and black stripes indicating 0
+ with the most-significant bit on top to indicate the page
+ number. In this way, every page will be unique and will consume
+ approximately 25 megabytes. Creating 200 pages like this will
+ make a file that is 5 GB.
+
+ - The file will have to have object streams since a regular xref
+ table won't be able to support offsets that large.
+
+ - A separate test program can create this file and do various
+ manipulations on it. This can be enabled with an environment
+ variable controlled by configure in much the same way image
+ comparison tests are enabled now. The argument to
+ --enable-large-file-test should be a path that has enough disk
+ space to do the tests, probably enough space for two coipes of
+ the file. The test program should also have an interactive mode
+ so we can generate the large file and then look at it with a
+ PDF viewer like Adobe Reader.
+
+ * Consider adding an example that uses the page APIs, or update the
+ documentation to refer the user to the test suite.
+
Soon
====
@@ -24,8 +53,6 @@ Soon
* See if I can support the new encryption formats mentioned in the
open bug on sourceforge. Check other sourceforge bugs.
- * Would be nice to confirm that it's working for > 4GB files.
-
* Splitting/merging concepts
newPDF() could create a PDF with just a trailer, no pages, and a