2010.01.15 13:40 "Re: [Tiff] eta for bigtiff support?", by Phil Harvey
- 2010.01.15 14:05 "Re: [Tiff] eta for bigtiff support?", by Leonard Rosenthol
-
2010.01.15 15:48 "Re: [Tiff] eta for bigtiff support?", by Adam Goode
-
2010.01.18 18:04 "Re: [Tiff] eta for bigtiff support?", by Phil Harvey
-
2010.01.19 16:15 "Re: [Tiff] eta for bigtiff support?", by Bob Friesenhahn
- 2010.01.19 17:29 "Re: [Tiff] eta for bigtiff support?", by Phil Harvey
- 2010.01.19 18:55 "Re: [Tiff] eta for bigtiff support?", by Toby Thain
- 2010.01.19 22:50 "Re: [Tiff] eta for bigtiff support?", by Christopher
-
2010.01.20 13:41 "Re: [Tiff] eta for bigtiff support?", by Gary McGath
-
2010.01.20 21:55 "Re: [Tiff] eta for bigtiff support?", by Chris Cox
- 2010.01.20 23:37 "Re: [Tiff] eta for bigtiff support?", by Gary McGath
-
2010.01.20 21:55 "Re: [Tiff] eta for bigtiff support?", by Chris Cox
-
2010.01.19 16:15 "Re: [Tiff] eta for bigtiff support?", by Bob Friesenhahn
-
2010.01.18 18:04 "Re: [Tiff] eta for bigtiff support?", by Phil Harvey
- 2010.02.04 17:35 "Re: [Tiff] eta for bigtiff support?", by Phil Harvey
2010.01.19 20:28 "Re: [Tiff] eta for bigtiff support?", by Olivier Paquet
The main concern is for cases where different applications would be usefully selected based on MIME type.
Exactly. The only case I can think of right now is a hypothetical "my mail reader displays TIFF inline but doesn't support BigTIFF so I want to launch an external application for that". This doesn't seem like a very good example so... any better ideas?
This needs to be weighed against the downsides of using a different MIME type. IMO: slower adoption by applications and perhaps user confusion. I'm uncertain how much this matters given the target audience for BigTIFF.
Olivier