From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: compface
Date: Tue, 15 Jan 2002 21:17:39 -0500 [thread overview]
Message-ID: <vxkpu4b82f0.fsf@cinnamon.vanillaknot.com> (raw)
In-Reply-To: <iluk7ujgrrj.fsf@extundo.com> (Simon Josefsson's message of "Tue, 15 Jan 2002 23:42:56 +0100")
Simon Josefsson <jas@extundo.com> writes:
> Any ideas?
See X-Face above. :-)
My compface simply doesn't like the leading 2 lines of C comment from
the icon format stage. I strip that out and compface is happy as can
be. I used xv(1) to size it down to 48x48 (with `S', followed by
smoothing it with `s') and then sicced this pipeline on it:
xbmtopbm < don5.xbm | pbmtoicon | tail +3 | compface > don5.xface
I'm still lost, however, on how one would create the high-niftitude
multi-plane X-Face-<digit>.
next prev parent reply other threads:[~2002-01-16 2:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-15 22:42 compface Simon Josefsson
2002-01-16 2:17 ` Karl Kleinpaste [this message]
2002-01-16 2:39 ` compface Lars Magne Ingebrigtsen
2002-01-16 2:54 ` compface John H. Palmieri
2002-01-16 4:03 ` compface Karl Kleinpaste
2002-01-16 5:52 ` compface Bill White
2002-01-16 6:56 ` compface Mark Trettin
2002-01-16 12:37 ` compface Simon Josefsson
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=vxkpu4b82f0.fsf@cinnamon.vanillaknot.com \
--to=karl@charcoal.com \
/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).