{
  "WorkItem": {
    "AffectedComponent": {
      "Name": "",
      "DisplayName": ""
    },
    "ClosedComment": "fixed in Changeset &#35;79043 .  This is a doc change.  First binary with this fix&#58;  v1.9.1.6.  ",
    "ClosedDate": "2011-06-13T11:17:53.977-07:00",
    "CommentCount": 0,
    "Custom": null,
    "Description": "I'm creating a zip file in memory with items also in memory. When I add a xml as a string entry and specify Encoding.UTF8 like this:\n \nzip.AddEntry(\"some_file.txt\", \"some data\", Encoding.UTF8);\n \nthen file has UTF-8 BOM prepended to it. Documentation for this function specifies that no byte-order-mark is emitted into the file. \n \n \nWhen I add file like this:\n \n \nzip.AddEntry(\"some_file.txt\", Encoding.UTF8.GetBytes(\"some data\"));\n \nthen there is no BOM. Library is latest stable, 1.9.1.5",
    "LastUpdatedDate": "2013-05-16T05:31:49.763-07:00",
    "PlannedForRelease": "",
    "ReleaseVisibleToPublic": false,
    "Priority": {
      "Name": "Low",
      "Severity": 50,
      "Id": 1
    },
    "ProjectName": "DotNetZip",
    "ReportedDate": "2010-04-21T08:54:00.197-07:00",
    "Status": {
      "Name": "Closed",
      "Id": 4
    },
    "ReasonClosed": {
      "Name": "Unassigned"
    },
    "Summary": "BOM in file contrary to the behavior described by the documentation",
    "Type": {
      "Name": "Issue",
      "Id": 3
    },
    "VoteCount": 1,
    "Id": 10681
  },
  "FileAttachments": [],
  "Comments": [
    {
      "Message": "Yes, good catch!",
      "PostedDate": "2010-06-02T15:56:02.66-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2011-06-13T11:17:53.977-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-02-21T18:43:34.507-08:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-05-16T05:31:49.763-07:00",
      "Id": -2147483648
    }
  ]
}