![]() NET Core removed most of the encodings to save space and CP437 is one of the ones removed because of its similarities to ASCII. This doc page describes the reasoning, but the gist of it is that. So CP437 (control character).Īs to Encoding support, I followed up with pallavit and confirmed the removal of CP437 was intentional. If the unicode bit is unset and the file name contains values outside of the shared ASCII/CP437 range, then those values will be interpreted as their numerical unicode equivalent. ![]() However, there is still the potential for discrepancies when reading a zip. ![]() Otherwise we write it in ASCII and leave the unicode bit unset. If a file name doesn't fit within the range of characters shared between CP437 and ASCII then we write it in unicode and set the zip unicode bit. In dotnet/corefx#9004 I added some checks to handle the unicode/CP437 file names issue. NET Core uses Encoding.Default, which seems incorrect)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |