{
  "WorkItem": {
    "AffectedComponent": {
      "Name": "",
      "DisplayName": ""
    },
    "ClosedComment": "no response.",
    "ClosedDate": "2009-05-08T09:32:43.67-07:00",
    "CommentCount": 0,
    "Custom": null,
    "Description": "We receive zipped files from IBM mainframes, The compressed files when decompressed contain IBM037 encoded data. When I use the DotNetZip dlls I receive an  InnerException: {\"  ZipFile::Read(): Bad signature (0x0C088B1F) at start of file at position 0x00000004\"}.  The only package that seems to handle this ZIP type seems to be PKZip. Winzip can not handle it.\n \nIs there a work-around supported by DotNetZip or can one be developed?",
    "LastUpdatedDate": "2013-05-16T05:32:28.013-07:00",
    "PlannedForRelease": "",
    "ReleaseVisibleToPublic": false,
    "Priority": {
      "Name": "Low",
      "Severity": 50,
      "Id": 1
    },
    "ProjectName": "DotNetZip",
    "ReportedDate": "2009-03-09T12:25:02.5-07:00",
    "Status": {
      "Name": "Closed",
      "Id": 4
    },
    "ReasonClosed": {
      "Name": "Unassigned"
    },
    "Summary": "DotNetZip Support for Archives generated on IBM Mainframe",
    "Type": {
      "Name": "Issue",
      "Id": 3
    },
    "VoteCount": 1,
    "Id": 7245
  },
  "FileAttachments": [],
  "Comments": [
    {
      "Message": "I could have a look at it, but I would need to be able to get my hands on those zip archives to see the formats.  Could you attach one here? Also if you have any doc at all on the format, that would be really useful too.  \r\n\r\nIBM037 is just EBCDIC, right?    Do you mean, the filenames are in EBCDIC?    DotNetZip doesn't really care about the encoding of the *content* of the files.  It's all just bytes to the compressor.  But it is important to use the correct codepage when *reading* a zip file, in order to properly parse the filenames and comments.    \r\n\r\nSo I guess what I'm saying is that if it's simply a matter of a code page, then it shouldn't be a problem, except obviously you ARE having a problem.  \r\n\r\nCouple ideas:\r\n- Are these zip files protected with encryption by any chance?  \r\n- could it be there's some header information on the file that  isn't really part of the zip standard?  (Normally zip files start with a different byte sequence than what is shown in the error message)\r\n\r\nAlso - very important - What version of DotNetZip are you using?\r\n\r\nsend me what you can.",
      "PostedDate": "2009-03-09T14:57:46.333-07:00",
      "Id": -2147483648
    },
    {
      "Message": "Yes IBM307 is EBCDIC. I believe that all filenames are also EBCDIC and this is causing the problem.\r\n\r\nThe error occurs on: Dim x As DOTZIP.ZipFile = DOTZIP.ZipFile.Read(_InputPath, Encoding.GetEncoding(\"IBM037\"))\r\n\r\nUnfortunately, these files are our client's property, so I'm not at liberty to release them.\r\n\r\nThere is no encryption on these files.\r\n\r\nI don't know about the header info, but PKZIP can read them.\r\n\r\nI'm using 1.7.2.12 of DotNetZip",
      "PostedDate": "2009-03-12T13:40:10.307-07:00",
      "Id": -2147483648
    },
    {
      "Message": "OK, you cannot show me the actual zip file.  Can you get me a *sample* zip file?   And are you clear that it does not matter if the CONTENT of the files is EBCDIC?  DotNetZip does not care about the encoding used inside the files contained in the archive.  The encoding used by DotNetZip has to do only with the filenames of the entries contained in the zip archive.  \r\n\r\nWithout an example of the failure, I'm going to have a hard time understanding what is going wrong, and an even harder time fixing it! ",
      "PostedDate": "2009-04-30T17:56:51.043-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2009-05-08T09:32:43.67-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-02-21T18:44:26-08:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-05-16T05:32:28.013-07:00",
      "Id": -2147483648
    }
  ]
}