mirror of
https://github.com/qpdf/qpdf.git
synced 2024-09-27 12:39:06 +00:00
Minor manual fixes
This commit is contained in:
parent
09a36ad62b
commit
b8ec4395e7
@ -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.
|
||||
|
||||
|
@ -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.
|
||||
|
Loading…
Reference in New Issue
Block a user