From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: [9fans] TIFF/libtiff
Date: Wed, 19 Mar 2008 06:54:14 +0200 [thread overview]
Message-ID: <35e4b7c7c611493af1356cbebbff1733@proxima.alt.za> (raw)
I have a working port of the libtiff library, version 3.8.2 and I'll
be looking to port 3.9.0beta as well as 4.0.0alpha in the next few
days.
I also have working tools,
--rwxrwxr-x M 43 lucio sys 499597 Mar 18 10:53 /386/bin/pub/tiff2bw
--rwxrwxr-x M 43 lucio sys 597885 Mar 18 10:53 /386/bin/pub/tiff2pdf
--rwxrwxr-x M 43 lucio sys 514702 Mar 18 10:53 /386/bin/pub/tiffcp
--rwxrwxr-x M 43 lucio sys 497835 Mar 18 10:53 /386/bin/pub/tiffdither
--rwxrwxr-x M 43 lucio sys 538938 Mar 18 10:53 /386/bin/pub/tiff2rgba
--rwxrwxr-x M 43 lucio sys 503646 Mar 18 10:53 /386/bin/pub/tiffcmp
--rwxrwxr-x M 43 lucio sys 535086 Mar 18 10:53 /386/bin/pub/tiff2ps
--rwxrwxr-x M 43 lucio sys 498334 Mar 18 10:53 /386/bin/pub/tiffset
--rwxrwxr-x M 43 lucio sys 497384 Mar 18 10:53 /386/bin/pub/tiffsplit
--rwxrwxr-x M 43 lucio sys 503927 Mar 18 10:53 /386/bin/pub/tiffdump
--rwxrwxr-x M 43 lucio sys 502360 Mar 18 10:53 /386/bin/pub/tiffmedian
--rwxrwxr-x M 43 lucio sys 508511 Mar 18 10:53 /386/bin/pub/tiffinfo
--rwxrwxr-x M 43 lucio sys 500656 Mar 18 10:54 /386/bin/pub/bmp2tiff
--rwxrwxr-x M 43 lucio sys 501633 Mar 18 10:54 /386/bin/pub/gif2tiff
--rwxrwxr-x M 43 lucio sys 502741 Mar 18 10:54 /386/bin/pub/fax2ps
--rwxrwxr-x M 43 lucio sys 500520 Mar 18 10:54 /386/bin/pub/fax2tiff
--rwxrwxr-x M 43 lucio sys 502814 Mar 18 10:54 /386/bin/pub/raw2tiff
--rwxrwxr-x M 43 lucio sys 498642 Mar 18 10:54 /386/bin/pub/ppm2tiff
--rwxrwxr-x M 43 lucio sys 498565 Mar 18 10:54 /386/bin/pub/pal2rgb
--rwxrwxr-x M 43 lucio sys 498243 Mar 18 10:54 /386/bin/pub/ras2tiff
--rwxrwxr-x M 43 lucio sys 500815 Mar 18 10:54 /386/bin/pub/thumbnail
--rwxrwxr-x M 43 lucio sys 539230 Mar 18 10:55 /386/bin/pub/rgb2ycbcr
but I don't know how to blend any of these with page(1), at the moment
the solution seems to be something like
tiff2ps xyz.tif | page
It would be preferable to let page do the deciding, but I'm not sure
how to approach this. Anybody who'd like to elighten me, please feel
free.
Mind you, I really believe page(1) needs some work, if only I could
figure out what are errors in it (partial black pages in TeX output,
for example) and what are misfeatures strictly from a personal point
of view.
++L
PS: I still really need to concoct and document the approach I use
more or less automatically now to produce APE libraries and tools, but
of course this is not the fun part, so it gets somewhat neglected. It
is also the reason why there are now two ports of "libtiff". Binaries
are easy to supply, sources need a bit of work.
next reply other threads:[~2008-03-19 4:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 4:54 lucio [this message]
2008-03-19 17:45 ` erik quanstrom
2008-03-19 19:02 ` lucio
2008-03-19 19:55 ` erik quanstrom
2008-03-19 20:22 ` lucio
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=35e4b7c7c611493af1356cbebbff1733@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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).