view release on metacpan or  search on metacpan

unzip-6.0/proginfo/extrafld.txt  view on Meta::CPAN

          was created.  This can happen if a utility renames the entry but
          does not update the UTF-8 path extra field.  If the CRC check fails,
          this UTF-8 Path Extra Field should be ignored and the File Name field
          in the header should be used instead.

          The UnicodeName is the UTF-8 version of the contents of the File
          Name field in the header, without any trailing NUL.  The standard
          name field in the Zip entry header remains filled with the entry
          name coded in the local machine's extended ASCII system charset.
          As UnicodeName is defined to be UTF-8, no UTF-8 byte order mark
          (BOM) is used.  The length of this field is determined by
          subtracting the size of the previous fields from TSize.
          If both the File Name and Comment fields are UTF-8, the new General
          Purpose Bit Flag, bit 11 (Language encoding flag (EFS)), should be
          used to indicate that both the header File Name and Comment fields
          are UTF-8 and, in this case, the Unicode Path and Unicode Comment
          extra fields are not needed and should not be created.  Note that,
          for backward compatibility, bit 11 should only be used if the native
          character set of the paths and comments being zipped up are already
          in UTF-8.  The same method, either general purpose bit 11 or extra
          fields, should be used in both the Local and Central Directory Header

unzip-6.0/proginfo/extrafld.txt  view on Meta::CPAN

          The ComCRC32 is the standard zip CRC32 checksum of the Comment
          field in the central directory header.  This is used to verify that
          the comment field has not changed since the Unicode Comment extra
          field was created.  This can happen if a utility changes the Comment
          field but does not update the UTF-8 Comment extra field.  If the CRC
          check fails, this Unicode Comment extra field should be ignored and
          the Comment field in the header used.

          The UnicodeCom field is the UTF-8 version of the entry comment field
          in the header.  As UnicodeCom is defined to be UTF-8, no UTF-8 byte
          order mark (BOM) is used.  The length of this field is determined by
          subtracting the size of the previous fields from TSize.  If both the
          File Name and Comment fields are UTF-8, the new General Purpose Bit
          Flag, bit 11 (Language encoding flag (EFS)), can be used to indicate
          both the header File Name and Comment fields are UTF-8 and, in this
          case, the Unicode Path and Unicode Comment extra fields are not
          needed and should not be created.  Note that, for backward
          compatibility, bit 11 should only be used if the native character set
          of the paths and comments being zipped up are already in UTF-8.  The
          same method, either bit 11 or extra fields, should be used in both
          the local and central directory headers.