diff options
| author | Jay Berkenbilt <ejb@ql.org> | 2022-06-06 01:29:24 +0200 |
|---|---|---|
| committer | Jay Berkenbilt <ejb@ql.org> | 2022-06-06 01:34:28 +0200 |
| commit | 7cae125e6e1fa7a41ad17a3cd513fbd2d1ddc67e (patch) | |
| tree | ab4572387218c0c570454210bbeb5dad067825d5 /manual/json.rst | |
| parent | 057bd659bcbecee2ff8486f3659905f105ed6f53 (diff) | |
| download | qpdf-7cae125e6e1fa7a41ad17a3cd513fbd2d1ddc67e.tar.zst | |
JSON doc fixes and ideas based on discussion with m-holger
Diffstat (limited to 'manual/json.rst')
| -rw-r--r-- | manual/json.rst | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/manual/json.rst b/manual/json.rst index 960cccab..2e71bdab 100644 --- a/manual/json.rst +++ b/manual/json.rst @@ -12,12 +12,11 @@ Overview -------- Beginning with qpdf version 11.0.0, the qpdf library and command-line -program can produce a JSON representation of the in a PDF file. qpdf -version 11 introduces JSON format version 2. Prior to qpdf 11, -versions 8.3.0 onward had a more limited JSON representation -accessible only from the command-line. For details on what changed, -see :ref:`json-v2-changes`. The rest of this chapter documents qpdf -JSON version 2. +program can produce a JSON representation of a PDF file. qpdf version +11 introduces JSON format version 2. Prior to qpdf 11, versions 8.3.0 +onward had a more limited JSON representation accessible only from the +command-line. For details on what changed, see :ref:`json-v2-changes`. +The rest of this chapter documents qpdf JSON version 2. Please note: this chapter discusses *qpdf JSON format*, which represents the contents of a PDF file. This is distinct from the @@ -289,7 +288,8 @@ As such, none of the things ``QPDFWriter`` does apply. This includes recompression of streams, renumbering of objects, anything to do with object streams (which are not represented by qpdf JSON at all since they are PDF syntax, not semantics), encryption, decryption, -linearization, QDF mode, etc. +linearization, QDF mode, etc. See :ref:`rewriting` for a more in-depth +discussion. .. _json.example: |