diff options
| author | m-holger <m-holger@kubitscheck.org> | 2022-03-12 17:48:21 +0100 |
|---|---|---|
| committer | Jay Berkenbilt <jberkenbilt@users.noreply.github.com> | 2022-03-12 20:10:43 +0100 |
| commit | b8ec4395e740303c7046667f0c34478c8522520f (patch) | |
| tree | f84f95a2a7c0d263fe0019dc7785a8925276a81c | |
| parent | 09a36ad62bfa787642778b8076ae5b4ba4a64fcc (diff) | |
| download | qpdf-b8ec4395e740303c7046667f0c34478c8522520f.tar.zst | |
Minor manual fixes
| -rw-r--r-- | manual/design.rst | 6 | ||||
| -rw-r--r-- | manual/library.rst | 4 |
2 files changed, 5 insertions, 5 deletions
diff --git a/manual/design.rst b/manual/design.rst index f323aa75..07aaa875 100644 --- a/manual/design.rst +++ b/manual/design.rst @@ -105,7 +105,7 @@ and then reads the cross reference tables and trailer dictionaries. The read all of them so it can check the ``/Prev`` key. ``QPDF`` class users may request the root object and the trailer dictionary specifically. The cross reference table is kept private. Objects may then be requested by -number of by walking the object tree. +number or by walking the object tree. When a PDF file has a cross-reference stream instead of a cross-reference table and trailer, requesting the document's trailer @@ -254,7 +254,7 @@ resulting ``QPDFObjectHandle``. The calling object handle then replaces its ``PointerHolder<QDFObject>`` with the one from the newly returned ``QPDFObjectHandle``. In this way, only a single copy of any direct object need exist and clients can access objects transparently without -knowing caring whether they are direct or indirect objects. +knowing or caring whether they are direct or indirect objects. Additionally, no object is ever read from the file more than once. That means that only the portions of the PDF file that are actually needed are ever read from the input file, thus allowing the qpdf package to @@ -264,7 +264,7 @@ If the requested object is inside of an object stream, the object stream itself is first read into memory. Then the tokenizer reads objects from the memory stream based on the offset information stored in the stream. Those individual objects are cached, after which the temporary buffer -holding the object stream contents are discarded. In this way, the first +holding the object stream contents is discarded. In this way, the first time an object in an object stream is requested, all objects in the stream are cached. diff --git a/manual/library.rst b/manual/library.rst index ef63a2bb..33abdebe 100644 --- a/manual/library.rst +++ b/manual/library.rst @@ -10,7 +10,7 @@ Using QPDF from C++ The source tree for the qpdf package has an :file:`examples` directory that contains a few -example programs. The :file:`qpdf/qpdf.cc` source +example programs. The :file:`libqpdf/QPDFJob.cc` source file also serves as a useful example since it exercises almost all of the qpdf library's public interface. The best source of documentation on the library itself is reading comments in @@ -86,6 +86,6 @@ converted to ``wchar_t*``, and Unicode-aware Windows APIs are used. As such, qpdf will generally operate properly on files with non-ASCII characters in their names as long as the filenames are UTF-8 encoded for passing into the qpdf library API, but there are still some rough edges, -such as the encoding of the filenames in error messages our CLI output +such as the encoding of the filenames in error messages or CLI output messages. Patches or bug reports are welcome for any continuing issues with Unicode file names in Windows. |