2012 Jun 13, 3:08 2010 Mar 9, 9:08
I've just put up an update for Encode-O-Matic with the following improvements:
- Hex editor: the output and input views can now be switched between a UTF8 textbox view and a hex editor view. This is built using the free Be.HexEditor.
- Compression: I've added the .NET GZip, deflate, and inflate streams to the list of supported encodings.
- Quick Show Output: There are now 'Show Output' radio buttons next to each encoding in the encoding stack. Clicking on them changes the output view to show the output from that encoding in the
stack. This lets you easily jump between different parts of your encoding process. Adding or removing an encoding to the stack resets the view.
- Minor visuals improvement: added app icon, changed buttons with one word symbols to command names.
2010 Jan 20, 8:28
GZip vs Deflate execution speeds. Deflate found to be much faster in particular cases and about the same in the rest.
2009 Sep 3, 7:17
"This specification defines a lossless compressed data format that compresses data using a combination of the LZ77 algorithm and Huffman coding." Also see RFC 1950 zlib, a wrapper compression format
that can use deflate, and RFC 1952 gzip, a compressed file format that can use deflate.
2009 Sep 1, 4:39
"...what effect does the large-scale structure of the JS output code have on the DEFLATE algorithm of GZIP which is used to serve up compressed script?" Another instance of using knowledge of the
specific file type to get gains in compression. Is there a web proxy running all this at which I can point my phone?
2009 Sep 1, 4:36
"I’ve written a small Java application that will read in a CSS file and output its contents to stdout or another file in a format that’s optimised for gzipping." Cool!