diff options
Diffstat (limited to 'tqtinterface/qt4/src/3rdparty/libjpeg/libjpeg.doc')
| -rw-r--r-- | tqtinterface/qt4/src/3rdparty/libjpeg/libjpeg.doc | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/tqtinterface/qt4/src/3rdparty/libjpeg/libjpeg.doc b/tqtinterface/qt4/src/3rdparty/libjpeg/libjpeg.doc index bcd97d1..b50e716 100644 --- a/tqtinterface/qt4/src/3rdparty/libjpeg/libjpeg.doc +++ b/tqtinterface/qt4/src/3rdparty/libjpeg/libjpeg.doc @@ -1712,7 +1712,7 @@ reason for using progressive JPEG. The IJG encoder library generates progressive JPEG files when given a suitable "scan script" defining how to divide the data into scans. -Creation of progressive JPEG files is otherwise transtqparent to the encoder. +Creation of progressive JPEG files is otherwise transparent to the encoder. Progressive JPEG files can also be read transparently by the decoder library. If the decoding application simply uses the library as defined above, it will receive a final decoded image without any indication that the file was @@ -1759,7 +1759,7 @@ Progressive decompression: When buffered-image mode is not used, the decoder library will read all of a multi-scan file during jpeg_start_decompress(), so that it can provide a final decoded image. (Here "multi-scan" means either progressive or -multi-scan sequential.) This makes multi-scan files transtqparent to the +multi-scan sequential.) This makes multi-scan files transparent to the decoding application. However, existing applications that used suspending input with version 5 of the IJG library will need to be modified to check for a suspension return from jpeg_start_decompress(). |