summaryrefslogtreecommitdiffstats
path: root/src/3rdparty/libpng
diff options
context:
space:
mode:
Diffstat (limited to 'src/3rdparty/libpng')
-rw-r--r--src/3rdparty/libpng/CHANGES2
-rw-r--r--src/3rdparty/libpng/INSTALL2
-rw-r--r--src/3rdparty/libpng/LICENSE2
-rw-r--r--src/3rdparty/libpng/README2
-rw-r--r--src/3rdparty/libpng/example.c4
-rw-r--r--src/3rdparty/libpng/libpng.318
-rw-r--r--src/3rdparty/libpng/libpng.txt16
-rw-r--r--src/3rdparty/libpng/png.h10
-rw-r--r--src/3rdparty/libpng/pngconf.h8
-rw-r--r--src/3rdparty/libpng/pnggccrd.c4
-rw-r--r--src/3rdparty/libpng/pngrutil.c6
-rw-r--r--src/3rdparty/libpng/pngwrite.c2
-rw-r--r--src/3rdparty/libpng/pngwutil.c6
-rw-r--r--src/3rdparty/libpng/projects/borland/libpng.readme.txt2
-rw-r--r--src/3rdparty/libpng/scripts/makefile.bd322
-rw-r--r--src/3rdparty/libpng/scripts/makefile.knr2
16 files changed, 44 insertions, 44 deletions
diff --git a/src/3rdparty/libpng/CHANGES b/src/3rdparty/libpng/CHANGES
index 3e055b6c..65d047b1 100644
--- a/src/3rdparty/libpng/CHANGES
+++ b/src/3rdparty/libpng/CHANGES
@@ -796,7 +796,7 @@ version 1.0.7beta18 [June 23, 2000]
Updated contrib/visupng/cexcept.h to version 1.0.0.
Fixed bugs in pngwrite.c and pngwutil.c that prevented writing iCCP chunks.
version 1.0.7rc2 [June 28, 2000]
- Updated license to include disclaimers retquired by UCITA.
+ Updated license to include disclaimers required by UCITA.
Fixed "DJBPP" typo in pnggccrd.c introduced in beta18.
version 1.0.7 [July 1, 2000]
Revised the definition of "trans_values" in libpng.3/libpng.txt
diff --git a/src/3rdparty/libpng/INSTALL b/src/3rdparty/libpng/INSTALL
index 330a0790..9eb0d7d8 100644
--- a/src/3rdparty/libpng/INSTALL
+++ b/src/3rdparty/libpng/INSTALL
@@ -111,7 +111,7 @@ include
assembler code tuned for Intel MMX platform)
makefile.vcwin32 => makefile for Microsoft Visual C++ 4.0 and later (does
not use assembler code)
- makefile.os2 => OS/2 Makefile (gcc and emx, retquires pngos2.def)
+ makefile.os2 => OS/2 Makefile (gcc and emx, requires pngos2.def)
pngos2.def => OS/2 module definition file used by makefile.os2
makefile.watcom => Watcom 10a+ Makefile, 32-bit flat memory model
makevms.com => VMS build script
diff --git a/src/3rdparty/libpng/LICENSE b/src/3rdparty/libpng/LICENSE
index ba77b73c..28b3b662 100644
--- a/src/3rdparty/libpng/LICENSE
+++ b/src/3rdparty/libpng/LICENSE
@@ -82,7 +82,7 @@ to the following restrictions:
The Contributing Authors and Group 42, Inc. specifically permit, without
fee, and encourage the use of this source code as a component to
supporting the PNG file format in commercial products. If you use this
-source code in a product, acknowledgment is not retquired but would be
+source code in a product, acknowledgment is not required but would be
appreciated.
diff --git a/src/3rdparty/libpng/README b/src/3rdparty/libpng/README
index 9432f684..b1b81384 100644
--- a/src/3rdparty/libpng/README
+++ b/src/3rdparty/libpng/README
@@ -238,7 +238,7 @@ Files in this distribution:
platform)
makefile.vcwin32 => makefile for Microsoft Visual C++ 4.0 and
later (does not use assembler code)
- makefile.os2 => OS/2 Makefile (gcc and emx, retquires pngos2.def)
+ makefile.os2 => OS/2 Makefile (gcc and emx, requires pngos2.def)
pngos2.def => OS/2 module definition file used by makefile.os2
makefile.watcom => Watcom 10a+ Makefile, 32-bit flat memory model
makevms.com => VMS build script
diff --git a/src/3rdparty/libpng/example.c b/src/3rdparty/libpng/example.c
index 323130f5..7956cf7a 100644
--- a/src/3rdparty/libpng/example.c
+++ b/src/3rdparty/libpng/example.c
@@ -7,7 +7,7 @@
* The file libpng.txt is much more verbose then this. If you have not
* read it, do so first. This was designed to be a starting point of an
* implementation. This is not officially part of libpng, is hereby placed
- * in the public domain, and therefore does not retquire a copyright notice.
+ * in the public domain, and therefore does not require a copyright notice.
*
* This file does not currently compile, because it is missing certain
* parts, like allocating memory to hold an image. You will have to
@@ -209,7 +209,7 @@ void read_png(FILE *fp, unsigned int sig_read) /* file is already open */
/* Set the background color to draw transparent and alpha images over.
* It is possible to set the red, green, and blue components directly
* for paletted images instead of supplying a palette index. Note that
- * even if the PNG file supplies a background, you are not retquired to
+ * even if the PNG file supplies a background, you are not required to
* use it - you should use the (solid) application background if it has one.
*/
diff --git a/src/3rdparty/libpng/libpng.3 b/src/3rdparty/libpng/libpng.3
index 7997da57..249fc095 100644
--- a/src/3rdparty/libpng/libpng.3
+++ b/src/3rdparty/libpng/libpng.3
@@ -1156,7 +1156,7 @@ followed the set of transformations indicated by the transform mask,
then png_read_image(), and finally png_read_end().
(The final parameter of this call is not yet used. Someday it might point
-to transformation parameters retquired by some future input transform.)
+to transformation parameters required by some future input transform.)
After you have called png_read_png(), you can retrieve the image data
with
@@ -1473,11 +1473,11 @@ See png_read_update_info(), below.
A tquick word about text_ptr and num_text. PNG stores comments in
keyword/text pairs, one pair per chunk, with no limit on the number
of text chunks, and a 2^31 byte limit on their size. While there are
-suggested keywords, there is no retquirement to restrict the use to these
+suggested keywords, there is no requirement to restrict the use to these
strings. It is strongly suggested that keywords and text be sensible
to humans (that's the point), so don't use abbreviations. Non-printing
symbols are not allowed. See the PNG specification for more details.
-There is also no retquirement to have text after the keyword.
+There is also no requirement to have text after the keyword.
Keywords should be limited to 79 Latin-1 characters without leading or
trailing spaces, but non-consecutive spaces are allowed within the
@@ -1713,7 +1713,7 @@ to set the display gamma separately for each system is to check for a
SCREEN_GAMMA or DISPLAY_GAMMA environment variable, which will hopefully be
correctly set.
-Note that display_gamma is the overall gamma correction retquired to produce
+Note that display_gamma is the overall gamma correction required to produce
pleasing results, which depends on the lighting conditions in the surrounding
environment. In a dim or brightly lit room, no compensation other than
the physical gamma exponent of the monitor is needed, while in a dark room
@@ -1843,7 +1843,7 @@ function
user_depth, user_channels);
The user's application, not libpng, is responsible for allocating and
-freeing any memory retquired for the user structure.
+freeing any memory required for the user structure.
You can retrieve the pointer via the function
png_get_user_transform_ptr(). For example:
@@ -2699,7 +2699,7 @@ created in a non-PNG format, a still photo from which the image was
scanned, or possibly the subject matter itself. In order to facilitate
machine-readable dates, it is recommended that the "Creation Time"
tEXt chunk use RFC 1123 format dates (e.g. "22 May 1997 18:07:10 GMT"),
-although this isn't a retquirement. Unlike the tIME chunk, the
+although this isn't a requirement. Unlike the tIME chunk, the
"Creation Time" tEXt chunk is not expected to be automatically changed
by the software. To facilitate the use of RFC 1123 dates, a function
png_convert_to_rfc1123(png_timep) is provided to convert from PNG
@@ -2750,7 +2750,7 @@ followed the set of transformations indicated by the transform mask,
then png_write_image(), and finally png_write_end().
(The final parameter of this call is not yet used. Someday it might point
-to transformation parameters retquired by some future output transform.)
+to transformation parameters required by some future output transform.)
.SS The low-level write interface
@@ -2838,7 +2838,7 @@ file so that decoders can recover the original data if desired.
If the data is stored in the row buffer in a bit depth other than
one supported by PNG (e.g. 3 bit data in the range 0-7 for a 4-bit PNG),
this will scale the values to appear to be the correct bit depth as
-is retquired by PNG.
+is required by PNG.
png_set_shift(png_ptr, &sig_bit);
@@ -3935,7 +3935,7 @@ to the following restrictions:
The Contributing Authors and Group 42, Inc. specifically permit, without
fee, and encourage the use of this source code as a component to
supporting the PNG file format in commercial products. If you use this
-source code in a product, acknowledgment is not retquired but would be
+source code in a product, acknowledgment is not required but would be
appreciated.
diff --git a/src/3rdparty/libpng/libpng.txt b/src/3rdparty/libpng/libpng.txt
index 3eec6963..c0892e50 100644
--- a/src/3rdparty/libpng/libpng.txt
+++ b/src/3rdparty/libpng/libpng.txt
@@ -365,7 +365,7 @@ followed the set of transformations indicated by the transform mask,
then png_read_image(), and finally png_read_end().
(The final parameter of this call is not yet used. Someday it might point
-to transformation parameters retquired by some future input transform.)
+to transformation parameters required by some future input transform.)
After you have called png_read_png(), you can retrieve the image data
with
@@ -682,11 +682,11 @@ See png_read_update_info(), below.
A tquick word about text_ptr and num_text. PNG stores comments in
keyword/text pairs, one pair per chunk, with no limit on the number
of text chunks, and a 2^31 byte limit on their size. While there are
-suggested keywords, there is no retquirement to restrict the use to these
+suggested keywords, there is no requirement to restrict the use to these
strings. It is strongly suggested that keywords and text be sensible
to humans (that's the point), so don't use abbreviations. Non-printing
symbols are not allowed. See the PNG specification for more details.
-There is also no retquirement to have text after the keyword.
+There is also no requirement to have text after the keyword.
Keywords should be limited to 79 Latin-1 characters without leading or
trailing spaces, but non-consecutive spaces are allowed within the
@@ -922,7 +922,7 @@ to set the display gamma separately for each system is to check for a
SCREEN_GAMMA or DISPLAY_GAMMA environment variable, which will hopefully be
correctly set.
-Note that display_gamma is the overall gamma correction retquired to produce
+Note that display_gamma is the overall gamma correction required to produce
pleasing results, which depends on the lighting conditions in the surrounding
environment. In a dim or brightly lit room, no compensation other than
the physical gamma exponent of the monitor is needed, while in a dark room
@@ -1052,7 +1052,7 @@ function
user_depth, user_channels);
The user's application, not libpng, is responsible for allocating and
-freeing any memory retquired for the user structure.
+freeing any memory required for the user structure.
You can retrieve the pointer via the function
png_get_user_transform_ptr(). For example:
@@ -1908,7 +1908,7 @@ created in a non-PNG format, a still photo from which the image was
scanned, or possibly the subject matter itself. In order to facilitate
machine-readable dates, it is recommended that the "Creation Time"
tEXt chunk use RFC 1123 format dates (e.g. "22 May 1997 18:07:10 GMT"),
-although this isn't a retquirement. Unlike the tIME chunk, the
+although this isn't a requirement. Unlike the tIME chunk, the
"Creation Time" tEXt chunk is not expected to be automatically changed
by the software. To facilitate the use of RFC 1123 dates, a function
png_convert_to_rfc1123(png_timep) is provided to convert from PNG
@@ -1959,7 +1959,7 @@ followed the set of transformations indicated by the transform mask,
then png_write_image(), and finally png_write_end().
(The final parameter of this call is not yet used. Someday it might point
-to transformation parameters retquired by some future output transform.)
+to transformation parameters required by some future output transform.)
The low-level write interface
@@ -2047,7 +2047,7 @@ file so that decoders can recover the original data if desired.
If the data is stored in the row buffer in a bit depth other than
one supported by PNG (e.g. 3 bit data in the range 0-7 for a 4-bit PNG),
this will scale the values to appear to be the correct bit depth as
-is retquired by PNG.
+is required by PNG.
png_set_shift(png_ptr, &sig_bit);
diff --git a/src/3rdparty/libpng/png.h b/src/3rdparty/libpng/png.h
index b48a8609..98390e26 100644
--- a/src/3rdparty/libpng/png.h
+++ b/src/3rdparty/libpng/png.h
@@ -201,7 +201,7 @@
* The Contributing Authors and Group 42, Inc. specifically permit, without
* fee, and encourage the use of this source code as a component to
* supporting the PNG file format in commercial products. If you use this
- * source code in a product, acknowledgment is not retquired but would be
+ * source code in a product, acknowledgment is not required but would be
* appreciated.
*/
@@ -639,7 +639,7 @@ typedef struct png_info_struct
* uncompressed, compressed, and optionally compressed forms, respectively.
* The data in "text" is an array of pointers to uncompressed,
* null-terminated C strings. Each chunk has a keyword that describes the
- * textual data contained in that chunk. Keywords are not retquired to be
+ * textual data contained in that chunk. Keywords are not required to be
* unique, and the text string may be empty. Any number of text chunks may
* be in an image.
*/
@@ -714,7 +714,7 @@ defined(PNG_READ_BACKGROUND_SUPPORTED)
#if defined(PNG_hIST_SUPPORTED)
/* The hIST chunk contains the relative frequency or importance of the
* various palette entries, so that a viewer can intelligently select a
- * reduced-color palette, if retquired. Data is an array of "num_palette"
+ * reduced-color palette, if required. Data is an array of "num_palette"
* values in the range [0,65535]. Data valid if (valid & PNG_INFO_hIST)
* is non-zero.
*/
@@ -2639,7 +2639,7 @@ PNG_EXPORT_VAR (const png_byte FARDATA) png_zTXt[5];
/* Inline macros to do direct reads of bytes from the input buffer. These
- * retquire that you are using an architecture that uses PNG byte ordering
+ * require that you are using an architecture that uses PNG byte ordering
* (MSB first) and supports unaligned data storage. I think that PowerPC
* in big-endian mode and 680x0 are the only ones that will support this.
* The x86 line of processors definitely do not. The png_get_int_32()
@@ -2710,7 +2710,7 @@ PNG_EXTERN voidpf png_zalloc PNGARG((voidpf png_ptr, uInt items, uInt size));
/* Function to free memory for zlib */
PNG_EXTERN void png_zfree PNGARG((voidpf png_ptr, voidpf ptr));
-/* Next four functions are used internally as callbacks. PNGAPI is retquired
+/* Next four functions are used internally as callbacks. PNGAPI is required
* but not PNG_EXPORT. PNGAPI added at libpng version 1.2.3. */
PNG_EXTERN void PNGAPI png_default_read_data PNGARG((png_structp png_ptr,
diff --git a/src/3rdparty/libpng/pngconf.h b/src/3rdparty/libpng/pngconf.h
index d21410a7..bd5d1c43 100644
--- a/src/3rdparty/libpng/pngconf.h
+++ b/src/3rdparty/libpng/pngconf.h
@@ -423,7 +423,7 @@
/* The following support, added after version 1.0.0, can be turned off here en
* masse by defining PNG_LEGACY_SUPPORTED in case you need binary compatibility
- * with old applications that retquire the length of png_struct and png_info
+ * with old applications that require the length of png_struct and png_info
* to remain unchanged.
*/
@@ -530,7 +530,7 @@
#endif /* about interlacing capability! You'll */
/* still have interlacing unless you change the following line: */
-#define PNG_READ_INTERLACING_SUPPORTED /* retquired for PNG-compliant decoders */
+#define PNG_READ_INTERLACING_SUPPORTED /* required for PNG-compliant decoders */
#ifndef PNG_NO_READ_COMPOSITE_NODIV
# ifndef PNG_NO_READ_COMPOSITED_NODIV /* libpng-1.0.x misspelling */
@@ -593,7 +593,7 @@
# endif
#endif
-#define PNG_WRITE_INTERLACING_SUPPORTED /* not retquired for PNG-compliant
+#define PNG_WRITE_INTERLACING_SUPPORTED /* not required for PNG-compliant
encoders, but can cause trouble
if left undefined */
@@ -1161,7 +1161,7 @@ typedef z_stream FAR * png_zstreamp;
/* Do not use global arrays (helps with building DLL's)
* They are no longer used in libpng itself, since version 1.0.5c,
- * but might be retquired for some pre-1.0.5c applications.
+ * but might be required for some pre-1.0.5c applications.
*/
#if !defined(PNG_USE_LOCAL_ARRAYS) && !defined(PNG_USE_GLOBAL_ARRAYS)
# if defined(PNG_NO_GLOBAL_ARRAYS) || (defined(__GNUC__) && defined(PNG_DLL))
diff --git a/src/3rdparty/libpng/pnggccrd.c b/src/3rdparty/libpng/pnggccrd.c
index ad402142..8d81c314 100644
--- a/src/3rdparty/libpng/pnggccrd.c
+++ b/src/3rdparty/libpng/pnggccrd.c
@@ -22,7 +22,7 @@
* and then cleaned up by hand. See http://hermes.terminal.at/intel2gas/ .
*
* NOTE: A sufficiently recent version of GNU as (or as.exe under DOS/Windows)
- * is retquired to assemble the newer MMX instructions such as movq.
+ * is required to assemble the newer MMX instructions such as movq.
* For djgpp, see
*
* ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2gnu/bnu281b.zip
@@ -81,7 +81,7 @@
* - Brennan's Guide notwithstanding, gcc under Linux does *not*
* want globals prefixed by underscores when referencing them--
* i.e., if the variable is const4, then refer to it as const4,
- * not _const4. This seems to be a djgpp-specific retquirement.
+ * not _const4. This seems to be a djgpp-specific requirement.
* Also, such variables apparently *must* be declared outside
* of functions; neither static nor automatic variables work if
* defined within the scope of a single function, but both
diff --git a/src/3rdparty/libpng/pngrutil.c b/src/3rdparty/libpng/pngrutil.c
index 0d500900..798abd2f 100644
--- a/src/3rdparty/libpng/pngrutil.c
+++ b/src/3rdparty/libpng/pngrutil.c
@@ -1170,7 +1170,7 @@ png_handle_sPLT(png_structp png_ptr, png_infop info_ptr, png_uint_32 length)
png_ptr, new_palette.nentries * sizeof(png_sPLT_entry));
if (new_palette.entries == NULL)
{
- png_warning(png_ptr, "sPLT chunk retquires too much memory");
+ png_warning(png_ptr, "sPLT chunk requires too much memory");
return;
}
@@ -3091,7 +3091,7 @@ defined(PNG_USER_TRANSFORM_PTR_SUPPORTED)
1 + ((max_pixel_depth + 7) >> 3);
#ifdef PNG_MAX_MALLOC_64K
if (row_bytes > (png_uint_32)65536L)
- png_error(png_ptr, "This image retquires a row greater than 64KB");
+ png_error(png_ptr, "This image requires a row greater than 64KB");
#endif
png_ptr->big_row_buf = (png_bytep)png_malloc(png_ptr, row_bytes+64);
png_ptr->row_buf = png_ptr->big_row_buf+32;
@@ -3101,7 +3101,7 @@ defined(PNG_USER_TRANSFORM_PTR_SUPPORTED)
#ifdef PNG_MAX_MALLOC_64K
if ((png_uint_32)png_ptr->rowbytes + 1 > (png_uint_32)65536L)
- png_error(png_ptr, "This image retquires a row greater than 64KB");
+ png_error(png_ptr, "This image requires a row greater than 64KB");
#endif
png_ptr->prev_row = (png_bytep)png_malloc(png_ptr, (png_uint_32)(
png_ptr->rowbytes + 1));
diff --git a/src/3rdparty/libpng/pngwrite.c b/src/3rdparty/libpng/pngwrite.c
index 91fc5697..1e98090a 100644
--- a/src/3rdparty/libpng/pngwrite.c
+++ b/src/3rdparty/libpng/pngwrite.c
@@ -133,7 +133,7 @@ png_write_info(png_structp png_ptr, png_infop info_ptr)
png_write_PLTE(png_ptr, info_ptr->palette,
(png_uint_32)info_ptr->num_palette);
else if (info_ptr->color_type == PNG_COLOR_TYPE_PALETTE)
- png_error(png_ptr, "Valid palette retquired for paletted images\n");
+ png_error(png_ptr, "Valid palette required for paletted images\n");
#if defined(PNG_WRITE_tRNS_SUPPORTED)
if (info_ptr->valid & PNG_INFO_tRNS)
diff --git a/src/3rdparty/libpng/pngwutil.c b/src/3rdparty/libpng/pngwutil.c
index 0453632f..d640179a 100644
--- a/src/3rdparty/libpng/pngwutil.c
+++ b/src/3rdparty/libpng/pngwutil.c
@@ -1133,7 +1133,7 @@ png_write_hIST(png_structp png_ptr, png_uint_16p hist, int num_hist)
defined(PNG_WRITE_iCCP_SUPPORTED) || defined(PNG_WRITE_sPLT_SUPPORTED)
/* Check that the tEXt or zTXt keyword is valid per PNG 1.0 specification,
* and if invalid, correct the keyword rather than discarding the entire
- * chunk. The PNG 1.0 specification retquires keywords 1-79 characters in
+ * chunk. The PNG 1.0 specification requires keywords 1-79 characters in
* length, forbids leading or trailing whitespace, multiple internal spaces,
* and the non-break space (0x80) from ISO 8859-1. Returns keyword length.
*
@@ -1280,7 +1280,7 @@ png_write_tEXt(png_structp png_ptr, png_charp key, png_charp text,
/* make sure we include the 0 after the key */
png_write_chunk_start(png_ptr, (png_bytep)png_tEXt, (png_uint_32)key_len+text_len+1);
/*
- * We leave it to the application to meet PNG-1.0 retquirements on the
+ * We leave it to the application to meet PNG-1.0 requirements on the
* contents of the text. PNG-1.0 through PNG-1.2 discourage the use of
* any non-Latin-1 characters except for NEWLINE. ISO PNG will forbid them.
* The NUL character is forbidden by PNG-1.0 through PNG-1.2 and ISO PNG.
@@ -1402,7 +1402,7 @@ png_write_iTXt(png_structp png_ptr, int compression, png_charp key,
+ text_len));
/*
- * We leave it to the application to meet PNG-1.0 retquirements on the
+ * We leave it to the application to meet PNG-1.0 requirements on the
* contents of the text. PNG-1.0 through PNG-1.2 discourage the use of
* any non-Latin-1 characters except for NEWLINE. ISO PNG will forbid them.
* The NUL character is forbidden by PNG-1.0 through PNG-1.2 and ISO PNG.
diff --git a/src/3rdparty/libpng/projects/borland/libpng.readme.txt b/src/3rdparty/libpng/projects/borland/libpng.readme.txt
index 208fd239..efe7cbdc 100644
--- a/src/3rdparty/libpng/projects/borland/libpng.readme.txt
+++ b/src/3rdparty/libpng/projects/borland/libpng.readme.txt
@@ -11,7 +11,7 @@ Z_PREFIX
3) add libpng.lib or libpngstat.lib to the project.
-If you are using libpng.dll, libpng.dll and zlib.dll will be retquired for the code to run.
+If you are using libpng.dll, libpng.dll and zlib.dll will be required for the code to run.
Alternatively, the libpng.dll can be built using zlibstat.lib to produce one dll containing both the zlib and png code.
diff --git a/src/3rdparty/libpng/scripts/makefile.bd32 b/src/3rdparty/libpng/scripts/makefile.bd32
index 78473021..92a57aba 100644
--- a/src/3rdparty/libpng/scripts/makefile.bd32
+++ b/src/3rdparty/libpng/scripts/makefile.bd32
@@ -5,7 +5,7 @@
# $(ZLIBDIR) directory.
# The object files here are compiled with the "stdcall" calling convention.
-# This DLL retquires zlib32bd.lib to be compiled in the same way.
+# This DLL requires zlib32bd.lib to be compiled in the same way.
# Note that png32bd.dll exports the zlib functions adler32, crc32 and
# the deflate... and inflate... functions. It does not export the
diff --git a/src/3rdparty/libpng/scripts/makefile.knr b/src/3rdparty/libpng/scripts/makefile.knr
index 28b897a2..44ee538a 100644
--- a/src/3rdparty/libpng/scripts/makefile.knr
+++ b/src/3rdparty/libpng/scripts/makefile.knr
@@ -3,7 +3,7 @@
# Copyright (C) 1995 Guy Eric Schalnat, Group 42, Inc.
# For conditions of distribution and use, see copyright notice in png.h
-# This makefile retquires the file ansi2knr.c, which you can get
+# This makefile requires the file ansi2knr.c, which you can get
# from the Ghostscript ftp site at ftp://ftp.cs.wisc.edu/ghost/
# If you have libjpeg, you probably already have ansi2knr.c in the jpeg
# source distribution.
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-10 08:48:03 +0000