![]() ![]() So it might be changed to close each archive files when extract operation of each file is finished in rar extraction process.Īnd another issue related with zip password and Windows OEM & ANSI codepage when extracting files.Ĭurrent version of The Unarchiver can extract. I made a sample-test archive which has 256 split files and openmax CLI binary to check current system's OPEN_MAX limit. Then I found that The Unarchiver has been waiting to extract after openning all split files first.īut it is limited that openning over 256 files in one process, because the reason is the OSX's OPEN_MAX limits which is the value of concurrently opening files in one precess. So I asked the status when the problem was occured. I've been heard that someone can't extract. Hi, I hope you have been enjoying the end of the year. So I would like you to add feature that recognize zip format's 11th bit of general purpose flag. ![]() So when I designated specific filename encoding, it will try to extract only one encoding which I gave. We can classify these two different encoding.Ĭurrently in The Unarchiver, it might not aware of this difference. If filename can be encoded into windows related codepage( such as CP949 CP936.), it use these codepage.īut if filename can't be converted into local codepage, Winzip use Unicode filename.Īs a result, archive file has local codepage filename and Unicode filename in UTF-8.įortunately, when Unicode filename is used, 11th bit of general purpose bit flag is set. So when Winzip make archive file in particular locale windows, it use specific codepage filename and Unicode same time. ![]() Windows Winzip or other Unicode support zip application try to reserve maximum compatibility with legacy zip archive file. I would like to suggest feature for zip archive file. As a side benefit, produce some code that can be re-used to add archive support to Xee (so this whole project doesn't just steal time I could be working on Xee instead).įor actual information on the current state of this project, read on!.Have a simple and straightforward interface like BOMArchiveHelper.app.Handle non-UTF8 filenames, perferrably automatically.Not just Zip and Tar-Gzip, but RAR, 7-Zip, LhA, StuffIt, and anything else you can think of. Also, thanks to Windows' idiotic idea of using the current system encoding for filenames, I have tons of archives from Japan with Shift_JIS filenames, which none of the unarchivers on OS X I've tried will handle properly.Īnd so I, because I obviously don't have enough to do already, get the idea that I need to write a better unarchiver. Most other unarchivers on OS X have interfaces that I don't like, or just don't work very well. However, it has quite a number of limitations. I kind of like BOMArchiverHelper.app, the default OS X unzipping utility. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |