From 4400ce84eeb204cdcb35950dd8fde094fc249051 Mon Sep 17 00:00:00 2001
From: Jay Berkenbilt <ejb@ql.org>
Date: Thu, 21 Dec 2023 17:14:28 -0500
Subject: Add "n:/pdf-name" to qpdf JSON for binary names (fixes #1072)

---
 qpdf/qtest/qpdf-json.test | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

(limited to 'qpdf/qtest/qpdf-json.test')

diff --git a/qpdf/qtest/qpdf-json.test b/qpdf/qtest/qpdf-json.test
index 961b507a..9691d995 100644
--- a/qpdf/qtest/qpdf-json.test
+++ b/qpdf/qtest/qpdf-json.test
@@ -61,6 +61,7 @@ my @goodfiles = (
     'form-fields-and-annotations.pdf',
     'need-appearances.pdf',
     'fxo-blue.pdf',
+    'weird-tokens.pdf',
     );
 $n_tests += 6 * scalar(@goodfiles);
 
@@ -341,5 +342,21 @@ $td->runtest("check C API write to JSON stream",
              {$td->FILE => "auto-4"},
              {$td->FILE => "qpdf-ctest-47-4"});
 
+# Bugs #1072 and #1079 illustrate cases that qpdf-json got wrong. In
+# #1072, it was noticed that name tokens containing binary characters
+# (using #xx) would generate invalid JSON, even though qpdf's own JSON
+# parser would accept it. Also, the JSON spec allows real numbers in
+# scientific notation, but the PDF spec does not.
+$n_tests += 2;
+$td->runtest("handle binary names",
+             {$td->COMMAND =>
+                  "qpdf --json-output weird-tokens.pdf a.json"},
+             {$td->STRING => "", $td->EXIT_STATUS => 0});
+# Round-trip is tested above.
+$td->runtest("check json",
+             {$td->FILE => "a.json"},
+             {$td->FILE => "weird-tokens.json"},
+             $td->NORMALIZE_NEWLINES);
+
 cleanup();
 $td->report($n_tests);
-- 
cgit v1.2.3-54-g00ecf