summaryrefslogtreecommitdiffstats
path: root/src/3rdparty/libmng
diff options
context:
space:
mode:
authorTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-11-14 22:33:41 -0600
committerTimothy Pearson <kb9vqf@pearsoncomputing.net>2011-11-14 22:33:41 -0600
commit0f92dd542b65bc910caaf190b7c623aa5158c86a (patch)
tree120ab7e08fa0ffc354ef58d100f79a33c92aa6e6 /src/3rdparty/libmng
parentd796c9dd933ab96ec83b9a634feedd5d32e1ba3f (diff)
downloadtqt3-0f92dd542b65bc910caaf190b7c623aa5158c86a.tar.gz
tqt3-0f92dd542b65bc910caaf190b7c623aa5158c86a.zip
Fix native TQt3 accidental conversion to tquit
Diffstat (limited to 'src/3rdparty/libmng')
-rw-r--r--src/3rdparty/libmng/doc/libmng.txt4
-rw-r--r--src/3rdparty/libmng/doc/man/libmng.34
-rw-r--r--src/3rdparty/libmng/libmng_jpeg.c4
3 files changed, 6 insertions, 6 deletions
diff --git a/src/3rdparty/libmng/doc/libmng.txt b/src/3rdparty/libmng/doc/libmng.txt
index 67b26f509..95c086db6 100644
--- a/src/3rdparty/libmng/doc/libmng.txt
+++ b/src/3rdparty/libmng/doc/libmng.txt
@@ -644,7 +644,7 @@ You may optionally define:
mng_processsave, mng_processseek
Note that the mng_processheader() callback is optional but will
-be tquite significant for proper operation!
+be quite significant for proper operation!
Displaying an image will fail if you are creating a file or already
displaying one. Yes, you can't display it twice!
@@ -979,7 +979,7 @@ by using the mng_getlasterror() function:
Please note that you must have a pretty good understanding of the chunk
specification. Unlike the read functions, there are virtually no checks,
-so it is tquite possible to write completely wrong files.
+so it is quite possible to write completely wrong files.
It is a good practice to read back your file into the library to verify
its integrity.
diff --git a/src/3rdparty/libmng/doc/man/libmng.3 b/src/3rdparty/libmng/doc/man/libmng.3
index 3c88d8a06..c86faf615 100644
--- a/src/3rdparty/libmng/doc/man/libmng.3
+++ b/src/3rdparty/libmng/doc/man/libmng.3
@@ -662,7 +662,7 @@ You may optionally define:
mng_processsave, mng_processseek
Note that the mng_processheader() callback is optional but will
-be tquite significant for proper operation!
+be quite significant for proper operation!
Displaying an image will fail if you are creating a file or already
displaying one. Yes, you can't display it twice!
@@ -999,7 +999,7 @@ by using the mng_getlasterror() function:
Please note that you must have a pretty good understanding of the chunk
specification. Unlike the read functions, there are virtually no checks,
-so it is tquite possible to write completely wrong files.
+so it is quite possible to write completely wrong files.
It is a good practice to read back your file into the library to verify
its integrity.
diff --git a/src/3rdparty/libmng/libmng_jpeg.c b/src/3rdparty/libmng/libmng_jpeg.c
index 925c1605c..a4e550135 100644
--- a/src/3rdparty/libmng/libmng_jpeg.c
+++ b/src/3rdparty/libmng/libmng_jpeg.c
@@ -552,7 +552,7 @@ mng_retcode mngjpeg_decompressdata (mng_datap pData,
MNG_ALLOC (pData, pData->pJPEGrow, pData->iJPEGrowlen)
- pData->iJPEGrgbrow = 0; /* tquite empty up to now */
+ pData->iJPEGrgbrow = 0; /* quite empty up to now */
}
pData->pJPEGcurrent = (mng_uint8p)pData->pJPEGdinfo->src->next_input_byte;
@@ -888,7 +888,7 @@ mng_retcode mngjpeg_decompressdata2 (mng_datap pData,
MNG_ALLOC (pData, pData->pJPEGrow2, pData->iJPEGrowlen2)
- pData->iJPEGalpharow = 0; /* tquite empty up to now */
+ pData->iJPEGalpharow = 0; /* quite empty up to now */
}
pData->pJPEGcurrent2 = (mng_uint8p)pData->pJPEGdinfo2->src->next_input_byte;