home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!rosie!aozer
- From: aozer@next.com (Ali Ozer)
- Newsgroups: comp.sys.next.programmer
- Subject: Re: NeXT TIFF question
- Message-ID: <4482@rosie.NeXT.COM>
- Date: 26 Jul 92 21:23:21 GMT
- References: <17124@acorn.co.uk> <4481@rosie.NeXT.COM> <1992Jul26.060536.22698@csus.edu>
- Sender: news@NeXT.COM
- Organization: Next Computer, Inc.
- Lines: 28
-
- In article <1992Jul26.060536.22698@csus.edu> eps@cs.sfsu.edu writes:
- >In article <4481@rosie.NeXT.COM> aozer@next.com (Ali Ozer) writes:
- >>NeXTSTEP 2.x denotes alpha with the private MATTE tag; NeXTSTEP 3.0 uses
- >>the newly created standard ExtraSamples tag.
- >
- >You mean alpha tiff format changed *again*??? [Before 2.0 NeXT
- >used PhotoMetricInterpretation=5.] Arrgh!!!
- >
- > -=EPS=-
-
- But Eric, what's the problem? Our 3.0 images (with alpha) load under
- 2.0 just fine, and that was certainly the biggest concern...
-
- Our 1.0 alpha format was real crufty. 2.0 fixed that by using a
- private tag registered by SGI and used by Sam Leffler's library. As far
- as I know, no one but SGI and NeXT used that format. The TIFF 6.0 spec
- (just recently finalized) adopted a standard for alpha that was different
- and in NeXTSTEP 3.0 we decided to follow that.
-
- Ali
- Ali_Ozer@NeXT.com
-
-
-
-
-
-
-
-