Randomness and such
Categories: Travel, Cats, comics, CarsFixed: I noticed earlier today that Monster Cat was showing up crappily in Windows IE. (Because it’s been so long since I cared that I’d forgotten that it’s taboo just to resize images on the fly despite the fact that they look fine when you do that on the Mac…) So I re-exported and fixed that little problem tonight. The latest (2008) episodes should all display clearly and legibly now.
Suggestions? If you notice any other weirdness, feel free to comment. Also, I am not a comic artist so if you see something I could do better, please mention it!
Monster Cat! This will be week 3 of doing Monster Cat on Monday-Wednesday-Friday. I wonder how long I can keep that up. I already have 2 for next week and plan to build the 3rd before I leave for CT on Sunday.
Travel: Oh yeah, I’m going to be up in Connecticut Sunday evening through Thursday afternoon next week. Save me some snow, folks!
My car! Because what random, “late”-night post is complete without me gushing about my car? My Subaru turns 10 years old this week! Happy birthday, Green Hornet! Still under 155,000 miles, only 12,000 of which I’ve put on it in the last 5 years. Yeah, that tells you something about how radically my driving habits changed when I moved to Pennsylvania.
tags: car, monster cat, random, travel
January 24th, 2008 at 10:54 am
The Monster Cat uggliness you’re describing is caused by browsers using “nearest neighbor” algorithm to resize the image and is not Windows IE specific; it happens in all browsers, all platforms. Safari is unique (on both Mac and Windows) in that it does not use “nearest neighbor” algorithm but something more advanced.
The other reasons using the browser to resize is not a good idea is because you’re making the file much larger than it need be; why wait for a 1600 pixel wide image to download that will only be displayed 600 pixels wide? or if you’re using a small image and making it larger than you’re adding visual artifacts that will be inconsistent among browsers and almost always look bad. There are very, very few reasons to ever have the browser display an image at a size other than what it really is.
January 24th, 2008 at 11:01 am
Aha! Awesome - thanks! Mac Firefox apparently also uses a better algorithm too as that’s my browser of choice at the moment. (I’m tempted to go back to Safari…)
Once upon a time I knew better. Yes, I felt a little guilty for using the browser for re-sizing even if it was only around 100 pixels difference. *sigh* I remembered the “no matter what you set the size to the image is still x amount of data” part… but not the resizing ickiness.
Thank you for the explanation!
January 24th, 2008 at 9:32 pm
How about that, Mac Firefox does indeed not use nearest neighbor…I don’t remember it doing that, I wonder if it’s the newer versions have been updated or my memory is hazy…Mac Mozilla still uses nearest neighbor though.