Under a month is pretty quick, actually. That has to include reporting and discovery, verification, determining actual root cause (and how it was possible that it crept into 10.6.6), determining a safe fix, and finally verifying the fix through all hardware variations. And all known scenarios, taking into account that it wasn't just that something simple broke, but it touches the type rendering, PDF, and printing subsystems.

Apple must have thought it was serious enough to give it a high priority for such a fast track, because they didn't hold up this fix to include with the next 10.6.X release.

@Neutralzone Did you actually read what I wrote, I never said that a month delay was bad, I clearly stated that there was a month delay between the 10.6.7 release and the font update because the issue was complex and needed more time. Dear god, what is it with some people and their inability to read.

@Kawaii-Gardiner: Seems you should follow your own advice (or at least set-shift before you rant). I see Neutalzone simply embellished your "review". You took this as an affront to your brilliant "works as expected" review (which, you have to admit, is a bit of a snore). What is it with people and their inability to just be cool?

Oops, "for creating Dreamweaver documents" (I wish there was a correction feature for these reviews).