Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #34052
| From | Christian Heimes <christian@python.org> |
|---|---|
| Subject | Re: Imaging libraries in active development? |
| Date | 2012-11-29 09:37 +0100 |
| References | <ed0f3366-d0e9-4d87-94e0-d3fb48b34b65@googlegroups.com> <50B65486.8010306@gmail.com> <mailman.343.1354129246.29569.python-list@python.org> <slrnkbcvf9.1jc.grahn+nntp@frailea.sa.invalid> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.357.1354178262.29569.python-list@python.org> (permalink) |
Am 28.11.2012 22:11, schrieb Jorgen Grahn: > I thought those formats were dead since about a decade? (Ok, I know > TIFF has niches, but JPEG 2000?) Baseline TIFF is still used a lot when a lossless image format is required. It's widely used for scientific stuff, long-time preservation, health care (e.g. MRI) and for many more applications. If you need to deal with formats like 32bit float RGBA or 128bit complex float pixels or color spaces like CMYK, CIELUV, CIEXYZ, then TIFF is your man. I'm sitting on nearly a quarter petabyte of TIFF images. The data should still be usable in 200 years. Bit rot *is* a serious issue for long periods of time. > That seems like an argument for *not* having support for many file > formats in the imaging library itself -- just pipeline into the best > standalone utilities available. An imaging library shouldn't implement all file formats on its own and rather use existing libraries. That's what I'm doing with smc.freeimage. It wraps and ties together FreeImage and lcms. FreeImage itself contains and encapsulates eight libraries (e.g. libjpeg, libtiff4, libraw, libpng ...) in a powerful API. Christian
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Imaging libraries in active development? Alasdair McAndrew <amca01@gmail.com> - 2012-11-28 04:30 -0800
Re: Imaging libraries in active development? Michael Torrie <torriem@gmail.com> - 2012-11-28 11:14 -0700
Re: Imaging libraries in active development? Alasdair McAndrew <amca01@gmail.com> - 2012-11-28 22:53 -0800
Re: Imaging libraries in active development? Adrien <adnothing@gmail.com> - 2012-11-29 10:29 +0100
Re: Imaging libraries in active development? Alasdair McAndrew <amca01@gmail.com> - 2012-11-29 03:22 -0800
Re: Imaging libraries in active development? Alasdair McAndrew <amca01@gmail.com> - 2012-11-29 03:22 -0800
Re: Imaging libraries in active development? Alasdair McAndrew <amca01@gmail.com> - 2012-11-28 22:53 -0800
Re: Imaging libraries in active development? Christian Heimes <christian@python.org> - 2012-11-28 20:00 +0100
Re: Imaging libraries in active development? Jorgen Grahn <grahn+nntp@snipabacken.se> - 2012-11-28 21:11 +0000
Re: Imaging libraries in active development? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2012-11-28 19:27 -0500
Imaging library zoom <zoom@yahoo.com> - 2012-11-29 10:01 +0100
Re: Imaging libraries in active development? Christian Heimes <christian@python.org> - 2012-11-29 09:37 +0100
Re: Imaging libraries in active development? Nobody <nobody@nowhere.com> - 2012-11-29 18:45 +0000
RE: Imaging libraries in active development? "Prasad, Ramit" <ramit.prasad@jpmorgan.com> - 2012-11-29 23:04 +0000
csiph-web