* Duplicate current shiftjis.tbl as ms932.tbl
* Correct some wrong characters in shiftjis.tbl
* Remove bunch of non-shift-jis characters from shiftjis.tbl
* Add a missing character (819F=◆)
* Update pe.hexpat
Implementing a number of things and fixing others
* Update pe.hexpat
Adding the readonlyData pattern
* Update pe.hexpat
Testing putting the number of tabs on Github to 4 instead of 8 (so that comments on the code for the Sections don't break)
* Update pe.hexpat
Reverting change that turned out to be needless
* Update pe.hexpat
Actually sending the `products[while($ != richHeaderEndPosition)]` to `products[while($ < richHeaderEndPosition)]` change
* Add files via upload
Adding NE test file
* Add files via upload
Adding NE pattern file
* Update ne.hexpat
Fixing the error with the entry table assignment
* Update README.md
Added the NE pattern file to the list of patterns
* Update shiftjis.tbl
Deleted the very first character and changed the other first ones' values
* Update pe.hexpat
Implementing a number of things and fixing others
* Update pe.hexpat
Adding the readonlyData pattern
* Update pe.hexpat
Testing putting the number of tabs on Github to 4 instead of 8 (so that comments on the code for the Sections don't break)
* Update pe.hexpat
Reverting change that turned out to be needless
* Update pe.hexpat
Actually sending the `products[while($ != richHeaderEndPosition)]` to `products[while($ < richHeaderEndPosition)]` change
* Add files via upload
Adding NE test file
* Add files via upload
Adding NE pattern file
* Update ne.hexpat
Fixing the error with the entry table assignment
* Update README.md
Added the NE pattern file to the list of patterns
Previously, the zip pattern was searching for the end-of-central-directory
header signature (50 4B 05 06) by searching the entire file for it. This is
*very* slow for large files, and risks false positives since those bytes
could randomly appear in compressed data. I had this happen on the first
large (>2GB) zip file I tried.
I'm now checking for the EOCD signature at exactly 22 bytes from the end of
the file (in the common case there is no zip comment), and if that fails
I search for it in the last 64KB of the file (in case there *is* a comment
at the end of the EOCD, which can't be larger than 64KB). This is much
faster, and fixes loading my zip file where it was spuriously finding the
signature in the wrong place.
This still has a low risk of false positives (what if the comment has the
50 4B 05 06 bytes? what if there is a short comment but the signature
appears in the last 64KB of compressed data?), but I don't know what's the
"right" way to find the EOCD, or how proper zip-reading tools handle the
ambiguity...
* Use spaces instead of tabs in zip.hexpat
* patterns: minor cleanup to ZIP pattern
- Remove empty and unused CentralDirectoryEntry struct.
- Shorten the comment of CentralDirectoryFileHeader.fileOffset. It was so
long that the tooltip overflowed my screen, and didn't really add much
information.
- Small whitespace changes.
* Update pe.hexpat
Implementing a number of things and fixing others
* Update pe.hexpat
Adding the readonlyData pattern
* Update pe.hexpat
Testing putting the number of tabs on Github to 4 instead of 8 (so that comments on the code for the Sections don't break)
* Update pe.hexpat
Reverting change that turned out to be needless
* Update pe.hexpat
Actually sending the `products[while($ != richHeaderEndPosition)]` to `products[while($ < richHeaderEndPosition)]` change
