that zip format.Compatibility of my port; Compression:   - My port supports only the new Info-ZIP format (introduced     with this port). Therefore archives created by MacZip 1.0     (March 1999) must be extracted with this version or later     releases of Info-ZIP's UnZip to restore the complete set of     Macintosh attributes.Note: This port is complete unrelated to the shareware ZipIt.Even more, handling of special Macintosh attributes isincompatible with ZipIt. This port (MacZip) may be used toextract archives created by ZipIt, but make sure that youget the result as you expected.Macintosh Files; File Forks:----------------------------All Macintosh files comprise two forks, known as the datafork and the resource fork.  Unlike the bytes stored in theresource fork, the bytes in the data fork do not have toexhibit any particular internal structure. The applicationis responsible for interpreting the bytes in the data forkin whatever manner is appropriate. The bytes in the resourcefork usually have a defined internal structure and containdata object like menus, dialog boxes, icons and pictures.Although all Macintosh files contain both a data fork and aresource fork, one or both of these forks may be empty.MacZip stores data-forks and resource-forks separately. TheZipfile format does not allow to store two archive entriesusing exactly the same name. My solution is to modify thePath name of the resource-fork. All resource-fork names areprepended with a leading special directory named"XtraStuf.mac". So, when extracting on a Mac, you shouldnever see this directory "XtraStuf.mac" on your *disk*.On all foreign systems that support directories in filenames(e.g.: OS/2, Unix, DOS/Windows, VMS) you will get adirectory "XtraStuf.mac" when extracting MacZip archives.You can delete the complete directory "XtraStuf.mac" sinceMac resources do not make much sense outside the MacOSworld.Text encoding; Charsets of the Filenames:-----------------------------------------The following information is only important if you plan totransfer archives across different platforms/language systems:A typical Zip archive does not support different charsets.All filenames stored in the public area (= accessible byforeign systems other than MacOS) must be coded in thecharset ISO-8859-1 (CP1252 in the Microsoft Windows world)or CP850 (DOSLatin1). The latter should only be used by Zipprograms that mark the archive entries as "created underDOS". Apart from Macs, the commonly used platforms eithersupport ISO-8859-1 directly, or are compatible with it. Toachieve maximum compatibility, MacZip convert filenames fromthe Mac OS Roman character set to ISO-8859-1 and vice versa.But not every char of the charset MacRoman has theirequivalent in ISO-8859-1. To make the mapping in most casespossible, I chose most similar chars or at least the MIDDLEDOT.Mac OS Roman character set is used for at least thefollowing Mac OS localizations: U.S., British, CanadianFrench, French, Swiss French, German, Swiss German, Italian,Swiss Italian, Dutch, Swedish, Norwegian, Danish, Finnish,Spanish, Catalan, Portuguese, Brazilian, and the defaultInternational system.In all Mac OS encodings, character codes 0x00-0x7F areidentical to ASCII, except that  - in Mac OS Japanese, yen sign replaces reverse solidus  - in Mac OS Arabic, Farsi, and Hebrew, some of the    punctuation in this range is treated as having strong    left-right directionality, although the corresponding    Unicode characters have neutral directionalitySo, for best compatibility, confine filenames to the standard7-bit ASCII character set.If you generate a filename list of your archive (unzip -l),you will see the converted filenames. Your can also extractthe archive with the switch '-i' (= ignore mac filenames),and test your result.This MacZip port uses its own filename stored in thearchive. At the moment, the filename will be not converted.However, I'm planning to add support for Unicode.Currently, the following Mac OS encodings are NOT supported:Japanese, ChineseTrad, Korean, Arabic, Hebrew, Greek,Cyrillic, Devanagari, Gurmukhi, Gujarati, Oriya, Bengali,Tamil, Telugu Kannada, Malayalam, Sinhalese, Burmese, Khmer,Thai, Laotian, Georgian, Armenian, ChineseSimp, Tibetan,Mongolian, Ethiopic, Vietnamese, ExtArabic and finally:Symbol - this is the encoding for the font named "Symbol".Dingbats - this is the encoding for the font named "Zapf Dingbats".If you extract an archive coded with one of thesecharsets you will probably get filenames with funnycharacters.These problems apply only to filenames and NOT to the filecontent.of course: The content of the files will NEVER be converted !!File-/Creator Type:-------------This port uses the creator type 'IZip' and it is registeredat Apple (since 08. March 1998). File types can not beregistered any more. This port uses 'ZIP ' for Zip archivefiles. The creator 'IZip' type should be used for all futureversions of MacZip.Hints for proper restoration of file-time stamps:-------------------------------------------------UnZip requires the host computer to have proper time zoneinformation in order to handle certain tasks correctly (seeunzip.txt).  To set the time zone on the Macintosh, go tothe Map Control Panel and enter the correct number of hours(and, in a few locales, minutes) offset from UniversalTime/Greenwich Mean Time.  For example, the US Pacific timezone is -8 hours from UTC/GMT during standard (winter) timeand -7 hours from UTC/GMT during Daylight Savings Time.  TheUS Eastern time zone is -5 hours during the winter and -4hours during the summer.Discussion of Daylight Savings Time-----------------------------------The setting in the Date & Time control panel for DaylightSavings time is a universal setting. That is, it assumeseverybody in the world is observing Daylight Savings timewhen its check box is selected.If other areas of the world are not observing DaylightSavings time when the check box is selected in the Date &Time control panel, then the Map control panel will be offby an hour for all areas that are not recognizing DaylightSavings time.Conversely, if you set the Map control panel to an area thatdoes not observe Daylight Savings time and deselect/uncheckthe check box for Daylight Savings time in the Date & Timecontrol panel, then time in all areas celebrating DaylightSavings time will be off by an hour in the Map controlpanel.Example:     In the case of Hawaiians, sometimes they are three hours     behind Pacific Standard Time (PST) and sometimes two hours     behind Pacific Daylight Time (PDT). The Map control panel     can only calculate differences between time zones relative     to Greenwich Mean Time (GMT). Hawaii will always show up as     three hours past the Pacific time zone and five hours past     the Central time zone.     When Hawaiians are not observing Daylight Savings time, but     the rest of the country is, there is no combination of     settings in Map and Date & Time control panels which will     enable you to display Hawaiian local time correctly AND     concurrently display the correct time in other places that     do observe Daylight Savings time.     The knowledge about which countries observe Daylight Savings     time and which do not is not built into the Map control     panel, so it does not allow for such a complex calculation.     This same situation also occurs in other parts of the world     besides Hawaii. Phoenix, Arizona is an example of an area of     the U.S. which also does not observe Daylight Savings time.Conclusion:MacZip only knows the GMT and DST offsets of thecurrent time, not for the time in question.Projects & Packages:--------------------A Note to version numbers: Version of MacZip is currently1.06 and is based on the zip code version 2.3 and unzip codeversion 5.42. See About Box for current version and compilerbuild date.Because of the amount of sources I splitted this port intoseveral projects. See http://www.sitec.net/maczip forupdates.- core source parts:    unzxxx.zip    zipxxx.zip      These archives contains the main parts of the port. You can      build libraries and a standalone App with Metrowerks      standard console SIOUX. They contain only sources, no      executables. These archives are exact copies of the standard      Info-ZIP source distributions; they were only repackaged      under MacOS using MacZip, with one minor addition: For those      files that are stored in BinHex'ed format in the Info-ZIP      reference source archives, unpacked version that are ready      for use have been added.- additional source part:    MacZipxxx.zip: contains all the GUI stuff and the project      files to build the main-app.  Only sources of the GUI, no      zip or unzip code. To build MacZip successfully you will      need to also download the zip and unzip packages.- executables:    MacZipxxxnc.hqx: contains only executables and 'README.TXT',                     This version is without en-/decryption support !    MacZipxxxc.hqx:  contains only executables and 'README.TXT',                     This version supports en-/decryption !- encryption sources:    zcryptxx.zip: To build crypt versions of MacZip.    download from ftp://ftp.icce.rug.nl/infozip/ (and subdirectories)- documentation:    MacZipDocu.zip: contains some further docus about the algorithm,                    limits, Info-ZIP's appnote and a How-to-do Webpage.Credits:--------Macstuff.c and recurse.c: All the functions are from More Files.More Files fixes many of the broken or underfunctional parts ofthe file system. Thanks to Jim Luther. (see morefiles.doc)---------------------------------------------------------------------------Footnotes:1. wild card:    The '*' is a wild card and means 'all files'    Just in case you don't know wild cards:    '*' is a place holder for any character.    e.g.:    "this*" matches with "this_file" or  "this_textfile" but it    doesn't match with "only_this_file" or  "first_this_textfile"    "*this*" matches with "this_file" or  "this_textfile" AND    matches with "only_this_file" or  "first_this_textfile"2. Mac pathnames:The following characteristics of Macintosh pathnames shouldbe noted:    A full pathname never begins with a colon, but must contain    at least one colon.    A partial pathname always begins with a colon separator except    in the case where the file partial pathname is a simple file or    directory name.    Single trailing separator colons in full or partial pathnames    are ignored except in the case of full pathnames to volumes.    In full pathnames to volumes, the trailing separator colon is    required.    Consecutive separator colons can be used to ascend a level    from a directory to its parent directory. Two consecutive    separator colons will ascend one level, three consecutive    separator colons will ascend two levels, and so on. Ascending    can only occur from a directory; not a file.---------------------------------------------------------------------------Dirk Haase==========