Archive-Unzip-Burst
view release on metacpan or search on metacpan
unzip-6.0/inflate.c view on Meta::CPAN
b) The previously unused distance codes #30 and #31 code distances
from 32769 to 49152 and 49153 to 65536. Both codes take 14 bits
of extra data to determine the exact position in their 16 kByte
range.
c) The last lit/length code #285 gets a different meaning. Instead
of coding a fixed maximum match length of 258, it is used as a
"generic" match length code, capable of coding any length from
3 (min match length + 0) to 65538 (min match length + 65535).
This means that the length code #285 takes 16 bits (!) of uncoded
extra data, added to a fixed min length of 3.
Changes a) and b) would have been transparent for valid deflated
data, but change c) requires to switch decoder configurations between
Deflate and Deflate64 modes.
*/
#define PKZIP_BUG_WORKAROUND /* PKZIP 1.93a problem--live with it */
/*
inflate.h must supply the uch slide[WSIZE] array, the zvoid typedef
(void if (void *) is accepted, else char) and the NEXTBYTE,
unzip-6.0/qdos/IZREADME.SMS view on Meta::CPAN
where src is a hard directory, would be stored in the zip directory as
src/split_name.c
It does handle '_' with a little intelligence.
The default UnZip option will be to translate '.' to '_'; this is
because there are still many QDOS/Minerva users that cannot handle '.'
without quotes, which is immensely inconvenient. For many SMS users
'_' is also the most natural and convenient option. It also means that
SMS/QDOS <-> SMS/QDOS Zip - UnZip sequences are transparent.
There will, however, be two ways around this in UnZip.
1. It is possible to Config the UnZip default to be '.'
translations (or not).
2. The UnZip -Q1 option will toggle the default (Config'ed)
state.
Examples:
unzip-6.0/vms/unzip_cli.help view on Meta::CPAN
| Success 0 Normal. No errors or warnings detected.
| Warning 1 One or more warnings were encountered, but
| processing completed successfully anyway.
| This includes archives where one or more
| (but not all) files were skipped because of
| unsupported compress or encrypt methods, or
| bad passwords.
| Error 2 Error in the archive format. Processing may
| have completed successfully anyway. Some
| defects in archives (made by other programs)
| can be repaired transparently.
| Fatal 3 Severe error in the archive format. Process-
| ing probably failed immediately.
| Fatal 4 Memory allocation failed in program initial-
| ization.
| Fatal 5 Memory allocation failed in password pro-
| cessing.
| Fatal 6 Memory allocation failed while decompressing
| to disk.
| Fatal 7 Memory allocation failed while decompressing
| in memory.
unzip-6.0/vms/unzip_def.rnh view on Meta::CPAN
Success 0 Normal. No errors or warnings detected.
Warning 1 One or more warnings were encountered, but
processing completed successfully anyway.
This includes archives where one or more
(but not all) files were skipped because of
unsupported compress or encrypt methods, or
bad passwords.
Error 2 Error in the archive format. Processing may
have completed successfully anyway. Some
defects in archives (made by other programs)
can be repaired transparently.
Fatal 3 Severe error in the archive format. Process-
ing probably failed immediately.
Fatal 4 Memory allocation failed in program initial-
ization.
Fatal 5 Memory allocation failed in password pro-
cessing.
Fatal 6 Memory allocation failed while decompressing
to disk.
Fatal 7 Memory allocation failed while decompressing
in memory.
( run in 0.461 second using v1.01-cache-2.11-cpan-a1d94b6210f )