diff options
| author | Masamichi Hosoda <trueroad@trueroad.jp> | 2019-09-26 16:36:14 +0200 |
|---|---|---|
| committer | Jay Berkenbilt <ejb@ql.org> | 2019-10-22 22:16:16 +0200 |
| commit | 5e0ba126871c57a8a688b36614f2b8d78c2675b3 (patch) | |
| tree | 3fe97fa23c0702e592d4a20c52b7da06cda8c0b5 /include | |
| parent | 3094955deeb2e8d3a9e325c3a47baffd6aea57ab (diff) | |
| download | qpdf-5e0ba126871c57a8a688b36614f2b8d78c2675b3.tar.zst | |
Fix /Contents value representation in a signature dictionary
Table 8.93 "Entries in a signature dictionary" in PDF 1.5 reference
describes that the value of Contents entry is a hexadecimal string
representation when ByteRange is specified.
This commit makes QPDF always uses hexadecimal strings representation
instead of literal strings for it.
Diffstat (limited to 'include')
| -rw-r--r-- | include/qpdf/QPDFWriter.hh | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/qpdf/QPDFWriter.hh b/include/qpdf/QPDFWriter.hh index c3818ae4..edea3c15 100644 --- a/include/qpdf/QPDFWriter.hh +++ b/include/qpdf/QPDFWriter.hh @@ -470,6 +470,7 @@ class QPDFWriter static int const f_stream = 1 << 0; static int const f_filtered = 1 << 1; static int const f_in_ostream = 1 << 2; + static int const f_hex_string = 1 << 3; enum trailer_e { t_normal, t_lin_first, t_lin_second }; |