From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Picon questions
Date: Sat, 12 Jan 2002 20:26:26 +0100 [thread overview]
Message-ID: <m3heprz7z1.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <vxk7kqnfkv6.fsf@cinnamon.vanillaknot.com>
Karl Kleinpaste <karl@charcoal.com> writes:
> The automatic picon creator referenced off the indiana.edu pages is
> AWOL, not accepting connections. Can someone tell me a suitable
> pipeline to convert a given face.gif to a picon-compatible colormap?
> They're supposed to be reduced to a 32-color set. I started using
> picons just today, and I'm using a mess of new *.gif that I've
> created, but they're surely not within the right color parameters as
> discussed at indiana.edu.
I'd suggest taking a file with known good colors (i.e., something from
the picons database that uses similar colors to what you want to use),
and then use "ppmquant -map that-file.ppm your-file.pmm" to convert
your file to use the same color map.
> Also, it seems to me that, once people have picked up the picon
> *.tar.Z files, they'll never again get them (they're huge). Is there
> any sort of auto-update scheme, I suppose in a subscription motif,
> where one could be notified of new picons' availability?
In the old version of the picons code, there were functions for
fetching picons off of the web. I haven't resurrected that code
yet...
But, no, I haven't heard of any auto-updating scheme. Beyond "apt-get
upgrade". :-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2002-01-12 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 19:08 Karl Kleinpaste
2002-01-12 19:26 ` Lars Magne Ingebrigtsen [this message]
2002-01-13 5:46 ` Daniel Pittman
2002-01-19 22:11 ` Lars Magne Ingebrigtsen
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=m3heprz7z1.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/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).