5 ms·
Actually, it is still true. hexdump has some confusing format options... what you were using was converting it to little-endian first before printing the hex re
by kbaker 8y ago
Actually, it is still true. hexdump has some confusing format options... what you were using was converting it to little-endian first before printing the hex representation, which really messed with gzip. Try this:
$ hexdump -e '"%x"' < american-english | gzip | wc -c
463871
$ hexdump -v -e '/1 "%02x"' < american-english | gzip | wc -c
302515
$ base64 < american-english | gzip | wc -c
415737
- eadmund 8y ago> converting it to little-endian first Ack, is there anything little-endian doesn't ruin? /me misses 68000 assembler …
- NelsonMinar 8y agoThanks! That'll teach me to cut and paste from StackExchange. Also why I got different results last time I looked at this; was using a different base 16 encoder.