IMPLEMENTATION_DETAILS.md in zip_kit-6.2.2 vs IMPLEMENTATION_DETAILS.md in zip_kit-6.3.0

@@ -76,11 +76,11 @@
 filename encoding scheme that is described here http://stackoverflow.com/questions/13261347
 you can try this:
 
    [Encoding::CP437, Encoding::ISO_8859_1, Encoding::UTF_8]
 
-We don't want no such thing, and sorry Windows users, you are going to need a decent unarchiver
-that honors the standard. Alas, alas.
+While this could work, we found it to be broken in practice as the decoding of the filename
+also depends on the system locale.
 
 Additionally, the tests with the unarchivers we _do_ support have shown that including the InfoZIP
 extra field does not actually help any of them recognize the file name correctly. And the use of
 those fields for the UTF-8 filename, per spec, tells us we should not set the EFS bit - which ruins
 the unarchiving for all other solutions. As any other, this decision may be changed in the future.
\ No newline at end of file