Lines Matching full:compressed
102 handling compressed data in the
193 replaced by a compressed version of itself, with the name
195 compressed file has the same modification date, permissions, and,
213 compressed output to a terminal, as this would be entirely
222 filename for the decompressed file from that of the compressed
263 compressed files. The result is the concatenation of the
265 (<computeroutput>-t</computeroutput>) of concatenated compressed
270 Multiple files may be compressed and decompressed like this. The
273 multiple compressed file representations. Such a stream can be
290 <para>Compression is always performed, even if the compressed
301 original. This guards against corruption of the compressed data,
314 to indicate a corrupt compressed file, 3 for an internal
466 compression is read from the header of the compressed file, and
469 stored in compressed files, it follows that the flags
491 <para>For files compressed with the default 900k block size,
517 for different block sizes. Also recorded is the total compressed
552 <para>The compressed representation of each block is delimited by
628 <computeroutput>bzip2</computeroutput>. Compressed data created by
632 above can correctly decompress multiple concatenated compressed files.
638 compressed files, so it could not handle compressed files more
789 occur whilst reading or writing the underlying compressed files,
855 robustness of the library to corrupted compressed data.</para>
964 of the compressed data has been read. The same is not true
979 the compressed data.</para></listitem>
986 sometimes useful to know when the compressed stream does not
996 error reading or writing in the compressed file, and by
1012 compressed file finishes before the logical end of stream is
1148 <para>Note that the compressed output generated is the same
1200 to be compressed, and <computeroutput>avail_in</computeroutput>
1209 point to a buffer in which the compressed data is to be placed,
1228 change of mode of the compressed stream.</para>
1230 <para>Conceptually, a compressed stream can be in one of four
1263 compressed and transferred to the output buffer. To do this,
1337 If all the existing input has been used up and all compressed
1350 If all the existing input has been used up and all compressed
1370 <listitem><para>Shovel data in and shlurp out its compressed form
1378 compressed output, until
1509 compressed data, and <computeroutput>avail_in</computeroutput>
1545 has detected the logical end of the compressed stream.
1565 if a data integrity error is detected in the compressed stream
1567 if the compressed stream doesn't begin with the right magic bytes
1639 error reading/writing the underlying compressed file, and you
1695 <para>Prepare to read compressed data from file handle
1775 (uncompressed) bytes from the compressed file
1798 copies data from the compressed file in chunks of size
1820 if there is an error reading from the compressed file
1822 if the compressed file ended before
1825 if a data integrity error was detected in the compressed stream
1869 <para>Returns data which was read from the compressed file but
1912 <para>Releases all memory pertaining to the compressed file
1948 <para>Prepare to write compressed data to file handle
2014 compressed and written to the file.</para>
2025 if there is an error writing the compressed file.
2050 <para>Compresses and flushes to the compressed file all data so
2054 illegal. All memory associated with the compressed file
2057 compressed file, but it is not
2065 <computeroutput>fflush</computeroutput> the compressed file. You
2074 total volume of compressed data written. For compatibility with
2089 if there is an error writing the compressed file
2097 <sect2 id="embed" xreflabel="Handling embedded compressed data streams">
2098 <title>Handling embedded compressed data streams</title>
2107 writes compressed data to it,
2111 compressed data stream, using that same file handle.</para></listitem>
2116 reads from the compressed file in blocks of size
2118 doing so probably will overshoot the logical end of compressed
2136 data forms the start of the next compressed stream. To start
2158 <para>Here's how you'd write data to a compressed file:</para>
2193 <para>And to read from a compressed file:</para>
2255 the compressed data, and <computeroutput>BZ_OK</computeroutput>
2256 is returned. If the compressed data won't fit,
2262 single call to this function. The resulting compressed data is a
2274 <para>To guarantee that the compressed data will fit in its
2296 if the size of the compressed data exceeds *destLen
2322 is returned. If the compressed data won't fit,
2339 <para>Because the compression ratio of the compressed data cannot
2363 if the size of the compressed data exceeds *destLen
2365 if a data integrity error was detected in the compressed data
2367 if the compressed data doesn't begin with the right magic bytes
2369 if the compressed data ends unexpectedly
2595 <sect1 id="limits" xreflabel="Limitations of the compressed file format">
2596 <title>Limitations of the compressed file format</title>
2604 incompatible compressed file format would create further
2648 <listitem><para>The compressed file format was never designed to be
2654 complexity could have been avoided if the compressed size of
2691 compressed file formats.</para>
2862 any compressed output, so this probably rules out applications
