From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] why is image(6) compression so poor?
Date: Wed, 19 Feb 2003 20:21:24 +0000 [thread overview]
Message-ID: <1c1bb0ba4a6765bbeba4ea5a77f928f7@vitanuova.com> (raw)
> 72+5996*7+3446 = 45280.
serves me right for not doing some simple arithmetic!
actually, it's interesting to observe that for small files
image(6) compression is sometimes better than gif.
overall though, its files seem to average about 50% bigger
(at least that's what the font images average).
it's probably worth it when the compression and decompression
routines combined come to only 272 lines!
next reply other threads:[~2003-02-19 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 20:21 rog [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-19 16:50 rog
2003-02-19 17:38 ` Russ Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1c1bb0ba4a6765bbeba4ea5a77f928f7@vitanuova.com \
--to=rog@vitanuova.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).