Introduction to UnZip
The UnZip package contains
ZIP extraction utilities. These are
useful for extracting files from ZIP
archives. ZIP archives are created
with PKZIP or Info-ZIP utilities, primarily in a DOS
environment.
This package is known to build and work properly using an LFS-7.4
platform.
![[Caution]](../images/caution.png)
Caution
The previous version of the UnZip package had some locale related
issues. Currently there are no BLFS editors capable of testing
these local issues. Therefore, the locale related information is
left on this page, but has not been tested. A more general
discussion of these problems can be found in the
Program Assumes Encoding section of the Locale Related Issues page.
Package Information
User Notes: http://wiki.linuxfromscratch.org/blfs/wiki/unzip
UnZip
Locale Issues
![[Note]](../images/note.png)
Note
Use of UnZip in the JDK, Mozilla, DocBook or any other BLFS package
installation is not a problem, as BLFS instructions never use
UnZip to extract a file with
non-ASCII characters in the file's name.
The UnZip package assumes that
filenames stored in the ZIP archives created on non-Unix systems
are encoded in CP850, and that they should be converted to
ISO-8859-1 when writing files onto the filesystem. Such assumptions
are not always valid. In fact, inside the ZIP archive, filenames
are encoded in the DOS codepage that is in use in the relevant
country, and the filenames on disk should be in the locale
encoding. In MS Windows, the OemToChar() C function (from
User32.DLL) does the correct
conversion (which is indeed the conversion from CP850 to a superset
of ISO-8859-1 if MS Windows is set up to use the US English
language), but there is no equivalent in Linux.
When using unzip to
unpack a ZIP archive containing non-ASCII filenames, the filenames
are damaged because unzip uses improper conversion
when any of its encoding assumptions are incorrect. For example, in
the ru_RU.KOI8-R locale, conversion of filenames from CP866 to
KOI8-R is required, but conversion from CP850 to ISO-8859-1 is
done, which produces filenames consisting of undecipherable
characters instead of words (the closest equivalent understandable
example for English-only users is rot13). There are several ways
around this limitation:
1) For unpacking ZIP archives with filenames containing non-ASCII
characters, use WinZip while running the Wine Windows emulator.
2) After running unzip, fix the damage made to the
filenames using the convmv tool (http://j3e.de/linux/convmv/). The
following is an example for the ru_RU.KOI8-R locale:
Step 1. Undo the conversion done by unzip:
convmv -f iso-8859-1 -t cp850 -r --nosmart --notest \
</path/to/unzipped/files>
Step 2. Do the correct conversion instead:
convmv -f cp866 -t koi8-r -r --nosmart --notest \
</path/to/unzipped/files>
Installation of UnZip
case `uname -m` in
i?86)
sed -i -e 's/DASM"/DASM -DNO_LCHMOD"/' unix/Makefile
make -f unix/Makefile linux
;;
*)
sed -i -e 's/CFLAGS="-O -Wall/& -DNO_LCHMOD/' unix/Makefile
make -f unix/Makefile linux_noasm
;;
esac
To test the results, issue: make
check.
Now, as the root user:
make prefix=/usr install
Command Explanations
sed ...: This command
ensures an obsolete system call is not made.
linux, linux_noasm: The
linux target in the Makefile makes
assumptions that are useful for a Linux system when compiling the
executables, but also uses some 32-bit x86 assembler code. The
linux_noasm target will build on all linux hosts. To obtain
alternatives to these targets, use make -f unix/Makefile list