Allow interoperability files with non-UTF-8 (bit 11 = 0) name #450
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
| Do you wish to fix those conflicts so we can merge it ? |
This was referenced Sep 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Commit based on #449. A separate PR is used to facilitate review.
This allows to read and write files with bit 11 (EFS) = 0 in any zip, with Buffer.
Multiple forks of the repo are used for this purpose, but not good enough. e.g. https://www.npmjs.com/package/adm-zip-iconv, https://www.npmjs.com/package/adm-zip-gbk, https://www.npmjs.com/package/jaswude-adm-zip, etc.