[
  {
    "Id": "222515",
    "ThreadId": "65338",
    "Html": "<p>Hi:</p>\r\n<p>I observed that files and folders with &Aacute; loose the accent when compressed (I'm in spanish, in spanish it's usual an &Aacute;). This not happened with lowercase &aacute; or other uppercase vocals I tested (I didn't tested all).</p>\r\n<p>Thanks</p>",
    "PostedDate": "2009-08-12T06:57:08.597-07:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  },
  {
    "Id": "222611",
    "ThreadId": "65338",
    "Html": "<p>Hello!</p>\r\n<p>Well.&nbsp; I am not a unicode expert, and I don't know the unicode requirements for encoding &Aacute;.&nbsp; BUT... I know something about Unicode and zip files.</p>\r\n<p>The default encoding for zip files is IBM437.&nbsp; If you write a simple application that uses DotNetZip, and you don't specify an encoding to use, then the zip file will encode file and folder names with the IBM437 code page.&nbsp;&nbsp;&nbsp;Now, IBM437 cannot encode all characters.&nbsp; For those characters it cannot encode, there is a conversion done.&nbsp;&nbsp; I&nbsp;don't know if &Aacute; can be encoded in IBM437.&nbsp; If it cannot, then you will likely get a loss of information in the conversion, like &Aacute;&nbsp;gets converted to A.</p>\r\n<p>To solve this problem, specify a value for ZipFile.UseUnicodeAsNecessary, or, specify ZipFile.ProvisionalAlternateEncoding, before adding any entries to a zip that you create.. Please read the documentation on those properties for a clear understanding of what they do, and the implications.</p>\r\n<p>If you are already setting one of those properties and still you are losing information in the filenames (like &Aacute;&nbsp;gets converted to A), then I'll have to take a closer look at your code.</p>\r\n<p>&nbsp;</p>",
    "PostedDate": "2009-08-12T10:08:20.033-07:00",
    "UserRole": null,
    "MarkedAsAnswerDate": null
  }
]