diff options
| author | Jay Berkenbilt <ejb@ql.org> | 2021-12-12 19:29:31 +0100 |
|---|---|---|
| committer | Jay Berkenbilt <ejb@ql.org> | 2021-12-13 17:20:14 +0100 |
| commit | 39779dd3c8e6fe12b32e44b70d595aea5fe941ea (patch) | |
| tree | f8744c00c29b48d6a6df1db0d9c74952c7f36c45 | |
| parent | 948c4546c8526d7e38dd7854356a233b58a994bc (diff) | |
| download | qpdf-39779dd3c8e6fe12b32e44b70d595aea5fe941ea.tar.zst | |
Minor doc cleanup, update spelling checker
| -rw-r--r-- | README.md | 2 | ||||
| -rw-r--r-- | cSpell.json | 11 |
2 files changed, 10 insertions, 3 deletions
@@ -104,7 +104,7 @@ QPDF is known to build and pass its test suite with mingw (latest version tested QPDF's build system, inspired by [abuild](https://www.qbilt.org/abuild), can optionally use its own built-in rules rather than using libtool and obeying the compiler specified with configure. This can be enabled by passing `--with-buildrules=buildrules` where buildrules corresponds to one of the `.mk` files (other than `rules.mk`) in the make directory. This should never be necessary on a UNIX system, but may be necessary on a Windows system. See [README-windows.md](README-windows.md) for details. -The QPDF package provides some executables and a software library. A user manual can be found in the "doc" directory. The docbook sources to the user manual can be found in the `manual` directory. +The QPDF package provides some executables and a software library. A user manual can be found in the "doc" directory. The sources to the user manual can be found in the `manual` directory. The software library is just `libqpdf`, and all the header files are in the `qpdf` subdirectories of `include` and `libqpdf`. If you link statically with `-lqpdf`, then you will also need to link with `-lz` and `-ljpeg`. The shared qpdf library is linked with `-lz` and `-ljpeg`, none of qpdf's public header files directly include files from `libz`, and only `Pl_DCT.hh` includes files from `libjpeg`, so for most cases, qpdf's development files are self contained. If you need to use `Pl_DCT` in your application code, you will need to have the header files for some libjpeg distribution in your include path. diff --git a/cSpell.json b/cSpell.json index 32026f36..76d51ee2 100644 --- a/cSpell.json +++ b/cSpell.json @@ -35,6 +35,7 @@ "bashcompinit", "berkenbilt", "binmode", + "bitstream", "blinearize", "boldseq", "bookinfo", @@ -81,8 +82,6 @@ "distclean", "distfiles", "ditems", - "docbook", - "docbookx", "docdir", "dohnal", "dqpdf", @@ -185,6 +184,8 @@ "jurczyk", "kgdl", "lastreleased", + "latexmk", + "latexpdf", "lbuf", "lcrypto", "ldflags", @@ -217,6 +218,7 @@ "makefiles", "masamichi", "mateusz", + "maxdepth", "mdash", "mkdir", "mkinstalldirs", @@ -284,6 +286,7 @@ "pbytes", "pclm", "pcre", + "pdflatex", "pdfs", "pdlin", "pfeifle", @@ -364,7 +367,9 @@ "rklength", "rpath", "rstream", + "runtest", "sahil", + "samp", "sarray", "scarff", "seekable", @@ -396,12 +401,14 @@ "syuu", "tbuf", "testcase", + "texlive", "tgen", "tiffcmp", "tmatrix", "tnum", "tobj", "tobjid", + "toctree", "toolchains", "transcoders", "trueroad", |