9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] PNG and APE (cntd)
Date: Thu, 27 Apr 2006 20:18:36 +0200	[thread overview]
Message-ID: <d6a13b4aa50be989cb25907dba68ecab@proxima.alt.za> (raw)
In-Reply-To: <33462a001ea97bcfca15659c3cb3607d@swtch.com>

> I remain unconvinced that all this effort on porting libpng
> isn't wasted time.  If the current png reading code doesn't
> work, I'd rather see that improved.  Andrey and I went through
> it a year ago and made it pass all the tests in the PNG suite.

Oh, the primary target is GeoTiff and the secondary one is Graphviz.
I'm trying to produce a marked-up map of the area I live in and the
format of the maps and aerial photographs I have sourced from the
South African Surveyor General's office are in GeoTiff format.

Since I needed zlib and libjpeg and GD wants libpng, it has been
instructive to cut my teeth on npng.  I had a recollection that png(1)
did not do 24-bit images, but no proof, so I went ahead and started
from a different end.

I did discover that PNG isn't widely used, that the patent on LZW has
expired and that I have plenty left to learn about graphics (thanks to
all contributors, not least forsyth for the Microsoft papers - td's
contribution does not need mention on this forum).

As for Breadpng(), there's no ways I'm going to study the actual
on-disk representation of PNG or any of the other formats without very
sound reason.  Life is way too short :-)

That does not mean that I do not appreciate the value of doing it, or
that I am not grateful to those who took it upon themselves to do it,
of course.  Philosophically, I'm at odds with the Plan 9 approach, but
it's a pragmatic decision.

++L



  reply	other threads:[~2006-04-27 18:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27  4:47 lucio
2006-04-27  6:23 ` Lluís Batlle i Rossell
2006-04-27 17:51   ` lucio
2006-04-27 18:24     ` Lluís Batlle i Rossell
2006-04-27 18:28     ` Charles Forsyth
2006-04-27 19:26       ` Jack Johnson
2006-04-27 19:58         ` Steve Simon
2006-04-27 21:13           ` Lluís Batlle i Rossell
2006-04-27 22:05             ` Charles Forsyth
2006-04-28  5:00               ` lucio
2006-04-28 18:31                 ` jmk
2006-04-27 20:02         ` Bruce Ellis
2006-04-27 19:59       ` lucio
2006-04-27  6:36 ` andrey mirtchovski
2006-04-27  6:39   ` andrey mirtchovski
2006-04-27 11:43   ` Lluís Batlle
2006-04-27 11:53     ` Harri Haataja
2006-04-27 12:25 ` Russ Cox
2006-04-27 12:25 ` Russ Cox
2006-04-27 18:18   ` lucio [this message]
2006-04-27 18:27     ` andrey mirtchovski
2006-04-27 19:56       ` 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=d6a13b4aa50be989cb25907dba68ecab@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).