From: forsyth@caldo.demon.co.uk forsyth@caldo.demon.co.uk
Subject: [9fans] XaoS - first useable version
Date: Wed, 10 Sep 1997 08:06:18 +0100 [thread overview]
Message-ID: <19970910070618.lhopx4mVDHCAZJPJTfJWvj6Jq_35WmtyeMK1LM6wRFc@z> (raw)
>>(IMO). As I saw in doc, plan9 has its own image format (pic) so I should
>>save it into it. But I din't found any library for that except tifflib,
>>wich looks rather strange and non-plan9ish. Is there any way to handle
there's a separate libfb (<fb.h>), which is the one that supports the
pic file format. man 2 wrbitmapfile describes the libg primitive
for writing Bitmaps to files. Plan 9's version of that routine doesn't
write a compressed format, unlike (say) Inferno's equivalent.
the pic file writer in libfb can write compressed pic files, though,
and you can then fiddle directly with images using the fb commands,
so on balance pic might be the best one to use.
next reply other threads:[~1997-09-10 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-09-10 7:06 forsyth [this message]
1997-09-10 7:42 forsyth
1997-09-10 9:03 Jan
1997-09-10 9:19 Jan
1997-09-10 17:11 forsyth
1997-09-10 17:28 Scott
1997-09-11 8:09 Jan
1997-09-11 8:12 Jan
1997-09-12 8:07 Jan
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=19970910070618.lhopx4mVDHCAZJPJTfJWvj6Jq_35WmtyeMK1LM6wRFc@z \
--to=forsyth@caldo.demon.co.uk \
/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).