aboutsummaryrefslogtreecommitdiffstats
path: root/manual/library.rst
diff options
context:
space:
mode:
authorm-holger <m-holger@kubitscheck.org>2022-03-12 17:48:21 +0100
committerJay Berkenbilt <jberkenbilt@users.noreply.github.com>2022-03-12 20:10:43 +0100
commitb8ec4395e740303c7046667f0c34478c8522520f (patch)
treef84f95a2a7c0d263fe0019dc7785a8925276a81c /manual/library.rst
parent09a36ad62bfa787642778b8076ae5b4ba4a64fcc (diff)
downloadqpdf-b8ec4395e740303c7046667f0c34478c8522520f.tar.zst
Minor manual fixes
Diffstat (limited to 'manual/library.rst')
-rw-r--r--manual/library.rst4
1 files changed, 2 insertions, 2 deletions
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.