{
  "WorkItem": {
    "AffectedComponent": {
      "Name": "",
      "DisplayName": ""
    },
    "ClosedComment": "fixed in changeset 79084.  First binary with this fix:  v1.9.1.6.",
    "ClosedDate": "2011-06-13T21:00:27.177-07:00",
    "CommentCount": 0,
    "Custom": null,
    "Description": "Hi,\n \nIn ZipEntry.Write.cs there appear to be some fixed length byte buffers that don't really take unicode into account. For example\n \nWriteHeader has this (ZipEntry.Write.cs, Line 703)\n \n \n            byte[] bytes = new byte[512];  // large enough for looooong filenames (MAX_PATH == 260)\n \n \n \nand this\n \n            byte[] FileNameBytes = _GetEncodedFileNameBytes();\n            Int16 filenameLength = (Int16)FileNameBytes.Length;\n \nWhen I pass in a unicode filename of say 148, I get back a byte buffer of 358.\n \nThe code should allocate a buffer based on filenameLength .",
    "LastUpdatedDate": "2013-05-16T05:31:36.31-07:00",
    "PlannedForRelease": "v1.9.1.8 DotNetZip - Latest Stable",
    "ReleaseVisibleToPublic": true,
    "Priority": {
      "Name": "Low",
      "Severity": 50,
      "Id": 1
    },
    "ProjectName": "DotNetZip",
    "ReportedDate": "2011-05-19T11:35:33.593-07:00",
    "Status": {
      "Name": "Closed",
      "Id": 4
    },
    "ReasonClosed": {
      "Name": "Unassigned"
    },
    "Summary": "Don't use hardcoded filename length in ZipEntry.Write.cs - Unicode filenames, max path",
    "Type": {
      "Name": "Issue",
      "Id": 3
    },
    "VoteCount": 1,
    "Id": 13542
  },
  "FileAttachments": [],
  "Comments": [
    {
      "Message": "I'm just interested why it was fixed?",
      "PostedDate": "2011-05-22T19:31:53.43-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2011-06-13T20:33:18.457-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2011-06-13T20:38:04.6-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2011-06-13T21:00:27.177-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-02-21T18:43:14.03-08:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-05-16T05:31:36.31-07:00",
      "Id": -2147483648
    }
  ]
}