Don’t use JPEG for logos… and don’t think you can solve the problem by re-saving the JPEG as a PNG

Once you go JPEG, you can’t go back.

You may recall having seen this previously on my blog:

DON'T USE JPEG FOR LOGOS…...USE PNG INSTEAD

I’ve been singing the “Don’t use JPEG for logos!” refrain for so long that most of my clients (and whoever they’re dealing with to deliver logo image files to them) know logos on the web should be in PNG format (or even better, SVG), not JPEG.

But a lot of people don’t seem to understand that you can’t turn a JPEG into a PNG.

Oh, sure, you can technically do that. By which I mean, you can open a JPEG in Photoshop or a similar image editing program, and save it as a PNG. But doing that won’t fix anything.

JPEG is a “lossy” format. That means that its compression algorithm permanently loses data about the image for the sake of a smaller file size. There’s no way to get that data back. PNG is not a lossy format, which means that it compresses the image data in a way that it can faithfully recreate the original input image.

So, what do you think happens when you open a JPEG and re-save it as a PNG? That’s right… it looks exactly like the JPEG did.

Like I said at the beginning, once you go JPEG, you can’t go back. The only option is to track down the original source image in a lossless format, or to manually clean up the results as best as you can.

I wish I could say I’ve never done this, but I’m a pragmatic individual, and I also like to try to solve problems myself… it’s often faster and easier than tracking down the original source. More times than I can remember, I have used the flood tool to turn splotchy logos back into blocks of solid color — doing my best to clean up the anti-aliased edges. And when the characteristics of the logo are right, I’ll often re-set the text in the original fonts (recognizing fonts by sight is a valuable skill), tweaking Bezier curves if the logo has any customizations, and then try my best to faithfully recreate object shapes by tracing them with the pen tool.

It’s perversely kind of fun, and I especially like when I can do it without even bothering to tell the client. They usually just care about the results, not about how the sausage gets made. Except when the client is an Italian restaurant. Then I let them worry about the sausage.

Ubuntu hits the big time, for real this time

Ubuntu LinuxI just finished installing Ubuntu Linux 9.04 on my MacBook under Parallels Desktop. In the past, I’ve ventured boldly into the realm of triple-boot configurations to allow my Mac to run Mac OS X, Windows XP and Ubuntu Linux. But that involves modifying firmware and overriding the standard boot process, plus splitting your drive into 3 partitions and reciting dark incantations by the light of the full moon whilst drinking the blood of a calf slain with a silver blade.

Well OK, not that last bit. I’m not sure where that comes from (oh right, that was the part about installing Windows on the Mac). But suffice to say, while it certainly could be done, setting up triple-boot was not for the faint of heart, and once it was working, the question of whether it was all worth it loomed large. And no, I cannot think in non-clichés tonight.

When I got my new MacBook a couple months ago, I decided my days of triple boot were over. I was just going to go by the book (see what I mean?) and use Boot Camp. Well, sort of by the book. Never one to take the easy road, I wasn’t just using Boot Camp, but also running Parallels Desktop. And while you certainly can run a valid Boot Camp installation of Windows XP with an OEM license (the cheapest way to go, courtesy of Newegg.com) both directly via Boot Camp and also with Parallels, Microsoft doesn’t make it easy for you. It involves calling an automated Microsoft support line, and reciting dark incantations by the light of the full moon — I mean reciting a 48-digit number displayed on your screen, answering four simple questions asserting that you have only installed Windows on one computer and you would never, ever, ever, ever lie to Microsoft or Steve Ballmer will bite the head off a live goat and put it in your bed while you sleep, and then typing in a new 48-digit number the automated system recites back to you, while it slays a calf with a silver blade, yadda yadda.

Now where was I?

Oh yeah, Ubuntu. A new version of Ubuntu Linux is released every six months, the latest version, 9.04 (so named for being released in April 2009, get it?), having arrived on the world’s virtual doorstep earlier this week. Ubuntu releases all have clever, alliterative codenames too. This one is Jaunty Jackalope. I’ve been following Ubuntu (via the triple-boot ritual) since Gutsy Gibbon (7.10), through last year’s releases of Hardy Heron (8.04) and Intrepid Ibex (8.10), the latter of which powers this website, thanks to Slicehost.

I’ve been more and more impressed with each release of Ubuntu, as the Ubuntu development team has polished the user experience — especially the once-nightmarish installation process — and as the GNOME team has simultaneously polished the desktop software most Ubuntu users live in day-to-day. While I’m still a die-hard Mac lover, I’ll admit Microsoft has been making major improvements with its GUI design (despite other notorious issues) with Vista, and Ubuntu/GNOME has been getting better and better with each new release as well. But I really feel like 9.04, Jaunty Jackalope, has finally crossed the line where Ubuntu Linux now feels to me every bit as polished, professional, usable and pleasing as a commercial OS. The installation process is far easier, and faster, than a Windows installation, and the overall experience of the interface is clean, intuitive, and responsive.

So it occurs to me, even in this age of netbooks and Microsoft’s (and to a much lesser extent, Apple’s, at least where the Mac is concerned — iPhone is definitely their top focus these days) recent floundering, while Linux, Ubuntu in particular, is making inroads, it’s still just not going to be embraced wholeheartedly as a viable desktop alternative.

Why is that? Well, obviously Microsoft doesn’t want that to happen. Linux really much more of a threat to Microsoft than it is to Apple. Even though all three OSes can run on Macs, people as a rule just aren’t buying Macs to not run Mac OS X. I’m sure it happens but… really… why? So the major hit to commercial OS developers comes when a user buys a non-Apple computer and decides to install and use Linux (Ubuntu or otherwise) as their primary/sole OS instead of Windows. So even as Linux, and the world of free, high-quality software that comes with it, reaches maturity, and Microsoft gives us an OS that is best known as the butt of jokes (not to mention viruses and malware of all sorts), why aren’t more people switching?

Ultimately there must be some software that users are relying on for Windows that they just can’t get for Linux. It’s the same argument often leveled against Macs: “not enough software.” It’s a straw man argument. Sure there is vastly more software written for Windows than for the other OSes, but 99.9% of that Windows-only software is: a) highly specialized tools for specific industries, b) utter crap, or usually c) both. Especially when we’re talking about consumer software, whatever it is you want to do can be done just as easily on Windows, Mac or Linux. The software exists. Often between Macs and Windows it’s the same software, ported from one OS to the other or developed concurrently. With Linux it’s usually open source alternatives that are every bit as feature-rich as their commercial counterparts.

Linux has decent free options for managing photos, listening to MP3s, editing video, and all of the office tasks covered by iLife and iWork on the Mac, or by Microsoft Office and the parade of unimaginatively named Microsoft tools or OEM add-on crapware that generally comes preinstalled on Windows PCs.

Except one.

No disrespect to the developers of GIMP, but the one software program Linux absolutely needs in order to be taken seriously as a desktop OS is Photoshop. That’s it. Once Adobe stops wasting its time writing terrible custom installers and decides instead to devote those resources to porting Creative Suite to Linux, it will be all over. Windows will never go away, I’m sure, but it will be reduced to a niche OS: it will live on mainly to support legacy point-of-sale systems and industrial fabrication applications and the other arcane and ugly commercial applications that companies generally deployed in huge numbers back in the Windows NT 3.51 era and have left untouched for more than a decade.

Adobe, it’s all up to you. You owe the world a karmic debt after Bridge.

Please, somebody, just tell me how to turn it off!

Yes, I drank Steve Jobs’ Kool-Aid a long time ago. I lined up at 4:30 on Friday outside an Apple Store to wait for 90 minutes for my copy of Mac OS X Leopard. I had read lots about it before it was released, so I knew what was coming. And yet, as much as I like most of the new features (especially the new Finder), and can put up with the things I like less (such as the cluttered-looking new Dock), I simply cannot stand the translucent menu bar.

Since I installed it yesterday, 90% of my computer time has been spent online trying to find out what I can do — whatever it takes — to just get back to a normal-looking, opaque menu bar. Why, oh why, Steve Jobs, can you not cede one tiny millimeter of interface control to the user? (OK, maybe I’m just bitter because I’ve spent the last week in the nirvana of user customization that is Ubuntu Linux.)

Judging by a Google search, it looks like I’m not alone in my frustration. But so far the only fixes I’ve seen are a hack app that only worked with the beta, and the somewhat obvious but equally lame option of incorporating a proper menu background as a band at the top of all of your desktop pictures.

Unfortunately, it looks like I won’t even be able to take the “somewhat obvious but equally lame” route, as it appears that Photoshop 7 (yes, it’s pitifully out-of-date, but it’s the version I own) doesn’t work in Leopard. D’oh!

Some more searching revealed a plausible, inexpensive alternative called Pixelmator. Of course, I am always dubious when someone posting on a forum or a blog comment says “this $59 shareware program can do everything Photoshop can do.” Um, yeah. Right. For less than 1/10 the price it was worth at least investigating though, so I downloaded the demo. It’s definitely a nice program, but it looks like the one thing I need most in Photoshop for the work I do, its layer effects, are completely missing from Pixelmator.

Update: Finally an elegant (if still fundamentally hackish) solution has presented itself, in the form of a little app called Opaque Menu Bar!

MNDOT’s secret to reining in highway construction costs: Photoshop

I was just reading, in the StarTribune online edition, an article about the lane addition project that was recently completed on Hwy. 100 in St. Louis Park.

The article includes a map and “Before” and “Now” photos, which I found very interesting. Especially when I noticed that the exact same cars were in both pictures, just in slightly different positions (all, that is, except for the red truck that appears to have been parked on the overpass for the entire duration of the construction project).

Imagine the coincidence, taking pictures both before and after the project, and timing it perfectly that the same cars would be traveling that stretch. Man, some people’s daily routines really are rigid! (Also, the weather was exactly the same, the photo was taken at the same time of day, the autumn leaves on the trees were at the same stage of coloration, etc.)

Of course, I think what’s really going on here is that the “Now” photo is actually a Photoshop mock-up produced by MNDOT during the proposal phase of the project. Anyone with an eye for Photoshop techniques can clearly see what’s been done to the photo. Still, it’s rather amusing that the Strib — intentionally or not — is passing this off as an actual photo of the road as it appears today.

Addendum (October 27, 2006; 9:15 PM): I figure since I took this opportunity to call attention to the Strib’s gaffe, I also owe it to them to share with my reader [sic] the fact that I also emailed the Strib about this, and in less than 12 hours I’ve received two emails from them — including one from the Director of Photography — apologizing for the mistake, and they say they’ll be posting a correction tomorrow. (Therefore, I’ll also refrain from capturing the erroneous version to post here.)

Addendum (November 7, 2006; 11:35 PM): Since I’m not a crackpot, I will not be pursuing this any further. However, I feel it’s worth at least noting here that I’ve just checked the page and no correction was ever made.