Article View: comp.sys.next.misc
Article #945Re: Non-standard TIFF format?
From: Allen B
Date: Mon, 10 Aug 1992 19:57
Date: Mon, 10 Aug 1992 19:57
29 lines
1593 bytes
1593 bytes
In article <92Aug10.151140.16671@acs.ucalgary.ca> bstone@acs.ucalgary.ca (Blake Stone) writes: > > I have now had two separate individuals complain to me about the > > apparent non-standard TIFF format coming out of NeXTstep > > applications. > > The problem usually isn't that the NeXT is generating > non-standard TIFF. The problem is that the TIFF standard is > soooo complex very few applications on other platforms implement > it correctly. (I haven't seen the TIFF 6.0 spec, but the 5.x > spec was about 60 pages long!). I have (121 pages, BTW), and it shows that things are going to get worse. (If you've ever heard me rant about TIFF before, imagine I just did it again. :-) ) To get around complexity, they've defined a subset (Baseline TIFF) for lazy people to implement. (I didn't say "sane" because sane people don't encourage use of TIFF.) Beats the multiple subsets in TIFF 5, but it shows they know they have a problem, but not that they plan to fix it. The new spec (should I put it on sonata/nova?) says that "Baseline TIFF" grayscale images should only be 4 or 8 bits. #@*! that! How could they leave 2 off that list? What the Hell were they thinking? ab
Technical Details
Message-ID:
<56482@mentor.cc.purdue.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!gatech!purdue!mentor.cc.purdue.edu!nova.cc.purdue.eduReferences:
<92Aug10.151140.16671@acs.ucalgary.ca>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!gatech!purdue!mentor.cc.purdue.edu!nova.cc.purdue.edu From: ab@nova.cc.purdue.edu (Allen B) Newsgroups: comp.sys.next.misc Subject: Re: Non-standard TIFF format? Message-ID: <56482@mentor.cc.purdue.edu> Date: 10 Aug 92 19:57:12 GMT References: <92Aug10.151140.16671@acs.ucalgary.ca> Sender: news@mentor.cc.purdue.edu Distribution: na Lines: 29