{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Ryan La Riviere <[EMAIL PROTECTED]>
On 02/18/2002 20:21, "Eric Peyton" <[EMAIL PROTECTED]> wrote:
> {#} Replies are directed back to [EMAIL PROTECTED]
> {#} To reply to the author, write to Eric Peyton <[EMAIL PROTECTED]>
>
>>>>
>>>
>>> % tiffutil -cat infile.tiff -out outfile.tiff
>>>
>>> Use that command on all the TIFFs and then check the new images in.
>>
>> That's a lot of TIFFs to go through.
>>
>
> Not at all ...
>
> cd Fire
> find . -name "*.tiff" -exec tiffutil -cat {} -out {} \;
>
> Done.
Yea... I gotta get better with figuring out that stuff. Man I love the
power of unix...just have to learn more.
There were only two TIFFs that were causing all the lines in my console.
fire128.tiff and fireblink.tiff
Now the console doesn't come up with all those errors.
It has also has made some of the other TIFFs smaller. :)
I also found that there was a TIFF that was missing the ff at the end...
./Contents/Resources/em_whatchutalkingabout_smile.tiff
Lastly, I got this:
2 images written to
./Contents/Resources/English.lproj/ConsoleWindow.nib/clean.tiff.
TIFF Error: Cannot read TIFF.
Error: Can't open
./Contents/Resources/English.lproj/Fire-macintosh.nib/NSAppleMenuImage.tiff.
Either it isn't a TIFF file, or there are unrecognized tags; try tiffutil
-dump for more info.
No output file created due to errors.
Same for all the other languages.
I got this when using a tiffutil -dump:
[neo:Resources/English.lproj/Fire-macintosh.nib] edljedi% tiffutil -dump
NSAppleMenuImage.tiff
Error while reading: TIFF headerError while reading: Not a TIFF file, bad
magic number
That's my story and I'm sticking to it.
--
Ryan "My hometown is nowhere, my friends are everywhere." La Riviere
System Administrator; Drexel University
215.895.6010
<http://staff.tdec.drexel.edu/~edljedi/>
{#} ----------------------------------------------------+[ fire ]+---
