New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Archives with undetected character sets #375
Comments
Thanks @gingerbeardman, the charset detection must be improved. My results where different though. In my tests:
|
Let's go with your test results. I'm not sure why mine were different. |
Just realized Keka has LHA extraction support but no format detection. I'm fixing that. |
Just an addition to this, whilst Keka extracts these files from #374 correctly, the incorrect charset is used for some filenames: |
Thanks @gingerbeardman! Already noted that on #374 (comment). It's incredible how many LHA variations there're. Do you think Japanese people still using it for compression? Or are those old files (like golden game gems) that still compressed in that format? |
LHA/LZH just really took off in Japan, because it was created by a Japanese guy. It's still used widely, in fact Windows 7 Japanese comes with LZH folder support! Not sure about Windows 10 Japanese but I assume it will still have it. |
@gingerbeardman version 1.1.13 just released with most LZH files properly extracted 😊 As for the EXE ones, I'll try to fix that one in #374. It is fairly more complicated to detect the compression method used in some EXE files. Thanks for the feedback as always! |
(I have to zip up the LZH archives to add them to GitHub)
Japanese
The text was updated successfully, but these errors were encountered: