You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a zip-archive which contains file names with Japanese characters.
When opening or extracting the archive with 7zip, the files are displayed with incorrect encoding:
The same happens when extracting the archive using bit7z.
I can, however, extract the files properly by using the "-mcp" option of 7z: 7z x -mcp=932 "スマトラ im11462659.zip"
(932 = Shift-JIS encoding)
As far as I can tell, there's currently no way to specify this option when using bit7z right now. Could this be added in a future update please?
As far as I can tell, there's currently no way to specify this option when using bit7z right now.
Yeah, it's not supported at the moment.
Could this be added in a future update please?
I think it is possible. The API that 7-Zip provides for setting the codepage wasn't very clear. But after reading 7-Zip's source code, I managed to understand how to achieve it and made a working proof-of-concept.
I still need to work out the optimal API and implementation.
I hope to add it for the next v4.0.9.
Feature description
I have a zip-archive which contains file names with Japanese characters.
When opening or extracting the archive with 7zip, the files are displayed with incorrect encoding:
The same happens when extracting the archive using bit7z.
I can, however, extract the files properly by using the "-mcp" option of 7z:
7z x -mcp=932 "スマトラ im11462659.zip"
(932 = Shift-JIS encoding)
As far as I can tell, there's currently no way to specify this option when using bit7z right now. Could this be added in a future update please?
The archive I've used for testing can be downloaded here: https://bowlroll.net/file/323005 (Scroll down for download button.)
I know about the solution using a manifest file mentioned here:
#163 (comment)
This does not work in my case, as I need a specific encoding for specific archive files only.
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: