From 8e361d98f0bb23d58cbc773367ba76dffced7bdb Mon Sep 17 00:00:00 2001
From: Jay Berkenbilt <ejb@ql.org>
Date: Sat, 18 Jun 2022 14:16:56 -0400
Subject: Add examples for output capture (fixes #691)

---
 TODO | 17 +----------------
 1 file changed, 1 insertion(+), 16 deletions(-)

(limited to 'TODO')

diff --git a/TODO b/TODO
index be29c58e..f71528e1 100644
--- a/TODO
+++ b/TODO
@@ -9,12 +9,12 @@ Before Release:
 * Release qtest with updates to qtest-driver and copy back into qpdf
 
 Next:
-* output capture
 * QPDFPagesTree -- avoid ever flattening the pages tree.
 * JSON v2 fixes
 
 Pending changes:
 
+* Allow users to supply a custom progress reporter for QPDFJob
 * Check about runpath in the linux-bin distribution. I think the
   appimage build specifically is setting the runpath, which is
   actually desirable in this case. Make sure to understand and
@@ -42,21 +42,6 @@ Pending changes:
 
 Soon: Break ground on "Document-level work"
 
-Output Capture + QPDFJob
-========================
-
-QPDFJob:
-
-* Allow users to supply a custom progress reporter for QPDFJob
-
-Output Capture
-
-See https://github.com/qpdf/qpdf/issues/691
-
-There needs to be a C API to QPDFLogger. Use functions like this:
-
-void set_info((*f)(char* data, unsigned int len, void* udata), void* udata);
-
 
 QPDFPagesTree
 =============
-- 
cgit v1.2.3-54-g00ecf