Lines Matching full:compressed
188 <dt><span class="sect2"><a href="#embed">3.4.8. Handling embedded compressed data streams</a></span></dt>
206 <dt><span class="sect1"><a href="#limits">4.1. Limitations of the compressed file format</a></span></dt>
225 handling compressed data in the
304 replaced by a compressed version of itself, with the name
306 compressed file has the same modification date, permissions, and,
322 compressed output to a terminal, as this would be entirely
330 compressed
361 compressed files. The result is the concatenation of the
363 (<code class="computeroutput">-t</code>) of concatenated compressed
367 Multiple files may be compressed and decompressed like this. The
370 multiple compressed file representations. Such a stream can be
384 <p>Compression is always performed, even if the compressed
394 original. This guards against corruption of the compressed data,
406 to indicate a corrupt compressed file, 3 for an internal
515 compression is read from the header of the compressed file, and
518 stored in compressed files, it follows that the flags
535 <p>For files compressed with the default 900k block size,
558 for different block sizes. Also recorded is the total compressed
586 <p>The compressed representation of each block is delimited by
649 <code class="computeroutput">bzip2</code>. Compressed data created by
653 above can correctly decompress multiple concatenated compressed files.
658 compressed files, so it could not handle compressed files more
726 <dt><span class="sect2"><a href="#embed">3.4.8. Handling embedded compressed data streams</a></span></dt>
827 occur whilst reading or writing the underlying compressed files,
883 robustness of the library to corrupted compressed data.</p>
965 of the compressed data has been read. The same is not true
977 the compressed data.</p></dd>
981 sometimes useful to know when the compressed stream does not
988 error reading or writing in the compressed file, and by
1001 compressed file finishes before the logical end of stream is
1115 <p>Note that the compressed output generated is the same
1151 to be compressed, and <code class="computeroutput">avail_in</code>
1159 point to a buffer in which the compressed data is to be placed,
1176 change of mode of the compressed stream.</p>
1177 <p>Conceptually, a compressed stream can be in one of four
1207 compressed and transferred to the output buffer. To do this,
1275 If all the existing input has been used up and all compressed
1288 If all the existing input has been used up and all compressed
1302 <li class="listitem"><p>Shovel data in and shlurp out its compressed form
1309 compressed output, until
1400 compressed data, and <code class="computeroutput">avail_in</code>
1432 has detected the logical end of the compressed stream.
1448 if a data integrity error is detected in the compressed stream
1450 if the compressed stream doesn't begin with the right magic bytes
1497 error reading/writing the underlying compressed file, and you
1543 <p>Prepare to read compressed data from file handle
1602 (uncompressed) bytes from the compressed file
1623 copies data from the compressed file in chunks of size
1642 if there is an error reading from the compressed file
1644 if the compressed file ended before
1647 if a data integrity error was detected in the compressed stream
1676 <p>Returns data which was read from the compressed file but
1704 <p>Releases all memory pertaining to the compressed file
1726 <p>Prepare to write compressed data to file handle
1772 compressed and written to the file.</p>
1780 if there is an error writing the compressed file.
1798 <p>Compresses and flushes to the compressed file all data so
1802 illegal. All memory associated with the compressed file
1805 compressed file, but it is not
1812 <code class="computeroutput">fflush</code> the compressed file. You
1820 total volume of compressed data written. For compatibility with
1832 if there is an error writing the compressed file
1836 <div class="sect2" title="3.4.8.?Handling embedded compressed data streams">
1838 <a name="embed"></a>3.4.8.?Handling embedded compressed data streams</h3></div></div></div>
1844 writes compressed data to it,
1848 compressed data stream, using that same file handle.</p></li>
1852 reads from the compressed file in blocks of size
1854 doing so probably will overshoot the logical end of compressed
1870 data forms the start of the next compressed stream. To start
1888 <p>Here's how you'd write data to a compressed file:</p>
1919 <p>And to read from a compressed file:</p>
1970 the compressed data, and <code class="computeroutput">BZ_OK</code>
1971 is returned. If the compressed data won't fit,
1976 single call to this function. The resulting compressed data is a
1986 <p>To guarantee that the compressed data will fit in its
2004 if the size of the compressed data exceeds *destLen
2023 is returned. If the compressed data won't fit,
2037 <p>Because the compression ratio of the compressed data cannot
2057 if the size of the compressed data exceeds *destLen
2059 if a data integrity error was detected in the compressed data
2061 if the compressed data doesn't begin with the right magic bytes
2063 if the compressed data ends unexpectedly
2227 <dt><span class="sect1"><a href="#limits">4.1. Limitations of the compressed file format</a></span></dt>
2236 <div class="sect1" title="4.1.?Limitations of the compressed file format">
2238 <a name="limits"></a>4.1.?Limitations of the compressed file format</h2></div></div></div>
2245 incompatible compressed file format would create further
2284 <li class="listitem" style="list-style-type: disc"><p>The compressed file format was never designed to be
2290 complexity could have been avoided if the compressed size of
2317 compressed file formats.</p>
2457 any compressed output, so this probably rules out applications
