Usually you hear people complaining that certain applications are available only on the PC side, and Mac users get screwed. In this case, the opposite is true. I’ve been a long-time user of products from Extensis, and I’ve used them on both Windows and OS X.I’ve been using Extensis Suitcase 9.2.2 for Windows for well over a year now. Prior to that I used Adobe Type Manager (ATM) Deluxe. I opted to go with Extensis’ offering because ATM Deluxe was no longer being supported by Adobe.Here’s the problem, though… Extensis Suitcase for Windows has been stuck at version 9.2.2 for at least a year, if not longer. In that time, Extensis has released the new Suitcase Fusion for OS X, which is lightyears ahead of the PC version. Where’s the love, Extensis? Maybe font management isn’t high up there for a lot of designers on the PC side, but your solution could be a lot better!A follow-up to this post can be found here: Font Management for Windows Made Easier
Author: Chris Harrison
-
Pandora’s Box
In the beginning there was Text, and it was good.
I’m still in awe about how much residual traffic I’ve gotten as a result of the conversation going on about how Microsoft Breaks HTML Email Rendering in Outlook 2007. The story, in various forms, has appeared on a number of sites. If you were to trust the comments on Digg, most people (it seems) would prefer that we revert back to a time where email is text-only. I don’t disagree that HTML emails can be evil, but there’s an inherent problem in wishing us back to the Stone Ages of Email: People like HTML email.
Yes, HTML email is abused by spammers. Yes, Incredimail sucks and so does “email stationary” in Outlook and the like… but if HTML email didn’t work (for spam or even legitimate correspondence), and if people didn’t want their messages to look *gag* “pretty”, there wouldn’t be a market for it.
HTML Email is here to stay, and that is why I am so irritated over the fact that Microsoft has taken to course action they have with Outlook 2007. Why break something that worked fine in older versions? Why take away something clients have come to expect?
Software should be improved from version to version. The choice to use the Word rendering engine in Outlook 2007 was probably predicated by a desire to avoid further anti-trust lawsuits… but that’s unexectable.
-
Google Talk + AOL Instant Messenger Integration
Google Talk + AOL Instant Messenger Integration – A brief update on the status of gTalk/AOL interoperability. Google: “We are working actively on integrating AIM access in Google Talk.”
-
Open Letter to Microsoft
Dear Microsoft,
Last year, you introduced Windows Internet Explorer 7 (IE7) upon the world. Designers everywhere celebrated the fact that you had finally stepped up to the standards plate. IE7 isn’t perfect, but it’s much better than what we had to work with.
Pretty soon, Outlook 2007 will be moved out of beta. One might assume that it, like it’s predecessors, would use IE for rendering HTML emails. (I know that I had.) But you know what? It doesn’t. It uses Word 2007 instead.
I know, I know. There will be lots of people out there that say HTML emails suck, and they’d be right. It’s probably safe to say that most spam email is of the HTML variety. But that shouldn’t be a problem for you, Microsoft, because IE7 should take care of any security issues that might arise, right?
HTML emails are a fact of life. Introducing another rendering engine to the mix makes life difficult for businesses like the one I work for. Email marketing is not our primary focus, but a lot of our customers want to stay in touch with their customers via email newsletters.
I shouldn’t have to worry about basic CSS stuff being supported in Outlook – stuff like background images, floats, stylized unordered lists, positioning, etc. should just work – but now I do.
Word 2007 is a word processor. Despite the fact that HTML can be generated from documents created within it, doesn’t make it a logical choice for rendering HTML – that is what Internet Explorer is for. Furthermore, this decision puts my confidence in IE7 in serious jeopardy: If you won’t even use it, why should I or anyone else for that matter?
It’s probably too late, but I hope you’ll reconsider this decision.
-
iNeedMore
Nothing kills productivity like a Keynote. Seriously.
Apple finally delivered an iPhone. Well, delivered is a bit of a stretch considering it won’t be until June 2007 before it will start hitting the shelves in Apple and Cingular stores. While I am really excited about the iPhone, and glad it’s finally here, I can’t help but think: “Where’s the rest of the announcements, Steve?” I know, I’m coming off as ungrateful. I mean, Steve invented the friggin iPod and just made the friggin iPhone. But really, is that it?
The Apple TV update was nice. I might have to buy one once it hits rev.2 and I get around to upgrading my home network to 802.11n. Apple will definitely have a place in my living room. I’ve already started to amass quite a collection of digital media that I’ve purchased off of iTunes, and it will be nice to be able to enjoy that content on my living room television.
The presentation on the iPhone was nice as well. It was very thorough. I mean, incredibly friggin’ thorough. Thorough to the point where it seemed like they had to stretch it out as long as possible in order to fill the two hour time slot alotted for the Keynote. I waited in anticipation for the “One More Thing…” The fact that the company formerly known as Apple Computer, Inc. is now Apple, Inc. wasn’t really much of a surprise. The fact that there were no additional announcements seemed more than a little odd to me.
People expected and, dare I say, demanded an Apple Phone. No amount of RDF would save Steve’s arse if he failed to deliver one. People expected an update on iTV, now known as Apple TV. Even with both of these great announcements, people still expected a lot more.
-
MacWorld Live Updates
If you’re like me and can’t wait to get the play-by-play on what’s going down at the MacWorld Expo, here are some sites where you’ll be able to get updates (via Glenn Wolsey). I’ll be checking in on MacRumors and Engadget, and will try to copy over some of the updates here as they occur.
Pictures from the event can be found on flickr, keyword: MacWorld2007.
-
Server Issues
I’ve been having some odd server issues since yesterday. MySQL has stopped responding a couple of times. So if my site goes offline for some reason, or you see a database error when visiting the site, this is likely the cause of it. Hopefully I can get the issue diagnosed and resolved over the weekend, because it is affecting client sites as well.
-
WordPress 2.0.6 Released
A new version of WordPress (2.0.6) has been released.
We have a pretty important release available for everyone, it includes an important security fix and it’s recommended that everyone upgrade. This is the latest release in our stable 2.0 line, which we’ve committed to maintaining for several more years.
Here’s what’s new:
- The aforementioned security fixes.
- HTML quicktags now work in Safari browsers.
- Comments are filtered to prevent them from messing up your blog layout.
- Compatibility with PHP/FastCGI setups.
I have updated to 2.0.6 and so far it’s run without any issues.
UPDATE: It looks like bbPress has just been updated as well.