From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: [9fans] why is image(6) compression so poor?
Date: Wed, 19 Feb 2003 16:50:31 +0000 [thread overview]
Message-ID: <d44f008d5d7dd69b7b0987c3c9baf223@vitanuova.com> (raw)
i recently observed that when writing a 500x500 all-white RGB24 image
in image(6) format, compressed, the resulting file is 45295 bytes.
gif compression, on the other hand, gives a file of 1689 bytes...
is this a bug, or a limitation of the compression scheme?
next reply other threads:[~2003-02-19 16:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 16:50 rog [this message]
2003-02-19 17:38 ` Russ Cox
2003-02-19 20:21 rog
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=d44f008d5d7dd69b7b0987c3c9baf223@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).