diff options
author | Jay Berkenbilt <ejb@ql.org> | 2010-06-06 17:45:02 +0200 |
---|---|---|
committer | Jay Berkenbilt <ejb@ql.org> | 2010-06-06 17:45:02 +0200 |
commit | 21753001b701ed2d3f48f73c1a2733b3a337fc99 (patch) | |
tree | fea5c834e72ab8673a97a6ddbff54d7a5c169360 /TODO | |
parent | 6c6227bf493167806540dce813a3ead457b8fd59 (diff) | |
download | qpdf-21753001b701ed2d3f48f73c1a2733b3a337fc99.tar.zst |
*** empty log message ***
git-svn-id: svn+q:///qpdf/trunk@978 71b93d88-0707-0410-a8cf-f5a4172ac649
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 7 |
1 files changed, 5 insertions, 2 deletions
@@ -32,7 +32,10 @@ General figure out why I added this to begin with and what in the code assumes it's the case. For enqueueObject and unparseChild in QPDFWriter, simply removing the checks for indirect scalars seems - sufficient. + sufficient. Looking back at the branch in the apex epub + repository, before flattening scalar references, there was special + case code in QPDFWriter to avoid writing out indirect nulls. It's + still not obvious to me why I did it though. To pursue this, remove the call to flattenScalarReferences in QPDFWriter.cc and disable the logic_error exceptions for indirect @@ -54,7 +57,7 @@ General If flattenScalarReferences is removed, a new method will be needed for checking PDF files. - * See if we can avoid preserving unreferenced objects in objet + * See if we can avoid preserving unreferenced objects in object streams even when preserving the object streams. * For debugging linearization bugs, consider adding an option to save |