image plugin - comparing favicon.ico

[bcswebstudio]

I recently tried the picture comparison plugin-- WOW. That's really slick stuff!!

In comparing favicon.ico (bookmarks/favorites images) files, however, even though bc knew to compare as images, it didn't like the formats and instead barked an error. I believe ico files can be a variety of formats, but typically they will either be gif or png. Is there a way the bc could try a couple before barking the error?

keep up the great work!
thanks

[Craig]

AFAIK, any file with the .ico file extension, including favicon.ico should be in the Windows Icon file format. To compare those files you should download the Symbol Viewer plugin (http://www.humbach-ac.de/html/EN/iconview.html) from Humbach Datentechnik. It supports icon (.ico) and cursor (.cur) files, including ones with multiple resolutions and bit depths.

[bcswebstudio]

Chris-
Thanks for the speedy reply-- sorry I missed it sooner.

The .ico which I'm referring to is a specific file ("favicon.ico" ) for the bookmark or favorites icons that FireFox always looks for and that Internet Explorer may look for (when directed or when adding a bookmark). To my knowledge, they can be any of the web formats: gif, jpg, png, and they differ entirely from Windows system .ico files.

thanks (off to check my reply-notification options now)

[Chris]

Right now the image viewer will only open a file if the file extension matches the actual format of the image. I'll add handling the .ico scenario to our wish list for a future release of the image viewer.

Posted by BCWebStudio:

That sounds great. I think all the relevant info is in the image's header (GIF89, JPEG, etc), but that's hopping out of my league..

Here's what I'm doing in the meantime, which seems to work. Thought I'd share with the forum for others to try:
- removed *.ico; from whatever it is associated with by default
- added new FileViewer and rather than matching a wildcard on extension, I put the complete string "favicon.ico".
Works like a charm. I hope future wildcard-match routines don't break this workaround :)

thanks