Spelling fixes

This commit is contained in:
Greg Sjaardema 2021-05-13 17:10:12 -06:00 committed by Hans Kristian Rosbach
parent 54b1c13c37
commit 5339a31cf9
12 changed files with 21 additions and 21 deletions

View File

@ -390,7 +390,7 @@ jobs:
wineboot --init
- name: Generate project files
# Shared libaries turned off for qemu ppc* and sparc & reduce code coverage sources
# Shared libraries turned off for qemu ppc* and sparc & reduce code coverage sources
run: |
mkdir ${{ matrix.build-dir || '.not-used' }}
cd ${{ matrix.build-dir || '.' }}

View File

@ -9,7 +9,7 @@ message(STATUS "Using CMake version ${CMAKE_VERSION}")
set(CMAKE_MACOSX_RPATH 1)
# If not specified on the command line, enable C99 as the default
# Configuration items that affect the global compiler envirionment standards
# Configuration items that affect the global compiler environment standards
# should be issued before the "project" command.
if(NOT CMAKE_C_STANDARD)
set(CMAKE_C_STANDARD 99) # The C standard whose features are requested to build this target

View File

@ -10,7 +10,7 @@
If your question is not there, please check the zlib home page
https://zlib.net/ which may have more recent information.
The lastest zlib FAQ is at https://zlib.net/zlib_faq.html
The latest zlib FAQ is at https://zlib.net/zlib_faq.html
1. Is zlib Y2K-compliant?

View File

@ -12,7 +12,7 @@ in a single application or system-wide.
Please note that zlib-ng in zlib-compat mode is API-compatible but not
ABI-compatible, meaning that you cannot simply replace the zlib library/dll
files and expect the application to work. The application will need to be
recompiled against the zlib-ng headers and libs to ensure full compatability.
recompiled against the zlib-ng headers and libs to ensure full compatibility.
**Advantages:**
- Easy to port to, since it only requires a recompile of the application and

View File

@ -9,7 +9,7 @@
# COMPARE - String to compare output against
# Optional Variables
# INPUT - Standard intput
# INPUT - Standard input
# IGNORE_LINE_ENDINGS - Ignore line endings when comparing output
if(NOT DEFINED OUTPUT OR NOT DEFINED COMPARE OR NOT DEFINED COMMAND)

View File

@ -10,7 +10,7 @@
# COMMAND - Command to run
# Optional Variables
# INPUT - Standard intput
# INPUT - Standard input
# OUTPUT - Standard output (default: /dev/null)
# SUCCESS_EXIT - List of successful exit codes (default: 0, ie: 0;1)

View File

@ -208,7 +208,7 @@ Z_INTERNAL void slide_hash_c(deflate_state *s) {
* o. the pointer advance forward, and
* o. demote the variable 'm' to be local to the loop, and
* choose type "Pos" (instead of 'unsigned int') for the
* variable to avoid unncessary zero-extension.
* variable to avoid unnecessary zero-extension.
*/
{
unsigned int i;

View File

@ -41,7 +41,7 @@ typedef struct {
/* Maximum size of the dynamic table. The maximum number of code structures is
1444, which is the sum of 852 for literal/length codes and 592 for distance
codes. These values were found by exhaustive searches using the program
examples/enough.c found in the zlib distribtution. The arguments to that
examples/enough.c found in the zlib distributions. The arguments to that
program are the number of symbols, the initial root table size, and the
maximum bit length of a code. "enough 286 9 15" for literal/length codes
returns returns 852, and "enough 30 6 15" for distance codes returns 592.

View File

@ -46,7 +46,7 @@ constantly downloading and building the old
version, you can check the .abi file into git.
To make this easier, a helper script could be written to automatically build
all the configurations tested by .github/worflows/abicheck.yml
all the configurations tested by .github/workflows/abicheck.yml
Then they could be checked into git en masse by a maintainer
when a new platform is added or a new major version (which
intentionally breaks backwards compatibility) is being prepared.

View File

@ -897,7 +897,7 @@ current difficulty in exchanging electronically computer-based
instructional software, which in turn makes it difficult for one scholar
to build upon the work of others, will be resolved before too long.
Stand-alone curricular applications that involve electronic text will be
sharable through networks, reinforcing their significance as intellectual
shareable through networks, reinforcing their significance as intellectual
products as well as instructional tools.
The second aspect of electronic learning involves the use of research and
@ -1587,7 +1587,7 @@ Bowdoin.
CALALUCA * PLD's principal focus and contribution to scholarship *
Various questions preparatory to beginning the project * Basis for
project * Basic rule in converting PLD * Concerning the images in PLD *
Running PLD under a variety of retrieval softwares * Encoding the
Running PLD under a variety of retrieval software * Encoding the
database a hard-fought issue * Various features demonstrated * Importance
of user documentation * Limitations of the CD-ROM version *
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
@ -1654,7 +1654,7 @@ anything demonstrated at the Workshop.
What cannot practically be done is go back and reconvert and re-encode
data, a time-consuming and extremely costly enterprise. CALALUCA sees
PLD as a database that can, and should, be run under a variety of
retrieval softwares. This will permit the widest possible searches.
retrieval software. This will permit the widest possible searches.
Consequently, the need to produce a CD-ROM of PLD, as well as to develop
software that could handle some 1.3 gigabyte of heavily encoded text,
developed out of conversations with collection development and reference
@ -5034,7 +5034,7 @@ schemes every single discrete area of a text that might someday be
searched. That was another decision. Searching by a column number, an
author, a word, a volume, permitting combination searches, and tagging
notations seemed logical choices as core elements. 3) How does one make
the data available? Tieing it to a CD-ROM edition creates limitations,
the data available? Tying it to a CD-ROM edition creates limitations,
but a magnetic tape file that is very large, is accompanied by the
encoding specifications, and that allows one to make local modifications
also allows one to incorporate any changes one may desire within the

View File

@ -273,7 +273,7 @@ int32_t zng_deflate(zng_stream *strm, int32_t flush);
== 0), or after each call of deflate(). If deflate returns Z_OK and with
zero avail_out, it must be called again after making room in the output
buffer because there might be more output pending. See deflatePending(),
which can be used if desired to determine whether or not there is more ouput
which can be used if desired to determine whether or not there is more output
in that case.
Normally the parameter flush is set to Z_NO_FLUSH, which allows deflate to
@ -655,7 +655,7 @@ int32_t zng_deflateGetDictionary(zng_stream *strm, uint8_t *dictionary, uint32_t
to dictionary. dictionary must have enough space, where 32768 bytes is
always enough. If deflateGetDictionary() is called with dictionary equal to
Z_NULL, then only the dictionary length is returned, and nothing is copied.
Similary, if dictLength is Z_NULL, then it is not set.
Similarly, if dictLength is Z_NULL, then it is not set.
deflateGetDictionary() may return a length less than the window size, even
when more than the window size in input has been provided. It may return up
@ -903,7 +903,7 @@ int32_t zng_inflateGetDictionary(zng_stream *strm, uint8_t *dictionary, uint32_t
to dictionary. dictionary must have enough space, where 32768 bytes is
always enough. If inflateGetDictionary() is called with dictionary equal to
NULL, then only the dictionary length is returned, and nothing is copied.
Similary, if dictLength is NULL, then it is not set.
Similarly, if dictLength is NULL, then it is not set.
inflateGetDictionary returns Z_OK on success, or Z_STREAM_ERROR if the
stream state is inconsistent.
@ -1438,7 +1438,7 @@ size_t zng_gzfread(void *buf, size_t size, size_t nitems, gzFile file);
provided, but could be inferred from the result of gztell(). This behavior
is the same as the behavior of fread() implementations in common libraries,
but it prevents the direct use of gzfread() to read a concurrently written
file, reseting and retrying on end-of-file, when size is not 1.
file, resetting and retrying on end-of-file, when size is not 1.
*/
Z_EXTERN Z_EXPORT

8
zlib.h
View File

@ -282,7 +282,7 @@ Z_EXTERN int Z_EXPORT deflate(z_stream *strm, int flush);
== 0), or after each call of deflate(). If deflate returns Z_OK and with
zero avail_out, it must be called again after making room in the output
buffer because there might be more output pending. See deflatePending(),
which can be used if desired to determine whether or not there is more ouput
which can be used if desired to determine whether or not there is more output
in that case.
Normally the parameter flush is set to Z_NO_FLUSH, which allows deflate to
@ -664,7 +664,7 @@ Z_EXTERN int Z_EXPORT deflateGetDictionary (z_stream *strm, unsigned char *dicti
to dictionary. dictionary must have enough space, where 32768 bytes is
always enough. If deflateGetDictionary() is called with dictionary equal to
Z_NULL, then only the dictionary length is returned, and nothing is copied.
Similary, if dictLength is Z_NULL, then it is not set.
Similarly, if dictLength is Z_NULL, then it is not set.
deflateGetDictionary() may return a length less than the window size, even
when more than the window size in input has been provided. It may return up
@ -901,7 +901,7 @@ Z_EXTERN int Z_EXPORT inflateGetDictionary(z_stream *strm, unsigned char *dictio
to dictionary. dictionary must have enough space, where 32768 bytes is
always enough. If inflateGetDictionary() is called with dictionary equal to
NULL, then only the dictionary length is returned, and nothing is copied.
Similary, if dictLength is NULL, then it is not set.
Similarly, if dictLength is NULL, then it is not set.
inflateGetDictionary returns Z_OK on success, or Z_STREAM_ERROR if the
stream state is inconsistent.
@ -1418,7 +1418,7 @@ Z_EXTERN size_t Z_EXPORT gzfread (void *buf, size_t size, size_t nitems, gzFile
provided, but could be inferred from the result of gztell(). This behavior
is the same as the behavior of fread() implementations in common libraries,
but it prevents the direct use of gzfread() to read a concurrently written
file, reseting and retrying on end-of-file, when size is not 1.
file, resetting and retrying on end-of-file, when size is not 1.
*/
Z_EXTERN int Z_EXPORT gzwrite(gzFile file, void const *buf, unsigned len);