I couldn't remember on Friday what it was that I wanted to report. I finally remembered the Saturday afternoon after. so once again, I'm posting it late and forging the date. no rhyme intended.
this bug is TIFF files not supported as bundle icons, an enhancement request. as usual, I did not modify it for the open web except to HTMLize.
Mac OS X only accepts IconFamily (icns) files as bundle (e.g. application) icons. Mac OS X should also accept TIFF files, which are more flexible and arguably easier to create (depending on your Terminal-fu).
Steps to Reproduce:
- create a bundle.
- place a TIFF file named “Icon.tiff” in the Contents/Resources subdirectory of the bundle.
- in Contents/Info.plist, set CFBundleIconFile to either “Icon.tiff” or “Icon”.
Mac OS X, upon noticing the bundle, recognizes the TIFF file as the bundle's icon. Finder uses as the bundle's icon the image from the TIFF whose dimensions most closely match the target icon size defined in View Options.
the bundle has a generic bundle or application icon.
an IconFamily file is limited to five resolutions: 16-pt, 32-pt, 48-pt, 128-pt, and 256-pt. also, the 256-pt resolution cannot be created with any current software. it is theoretically supported by the operating system, but no current application can create an IconFamily containing a 256-pt image — not even Icon Composer. tiffutil/tiffcp can and will easily add a 256-pt image to a TIFF file, or any other size image.
besides the obvious MIP-mapping advantages, TIFF also supports compression. images in a TIFF file can be compressed with JPEG, LZW, or PackBits, among other codecs. IconFamily does not support any compression. so given a TIFF file and an IconFamily file with the same set of images, the TIFF file would likely be smaller with the advantage of compression. this would also help ameliorate the disk-space hit of adding 256-pt images to some bundle icons.