Skip to content

Blog

DfontSplitter 0.4.1 for Mac

DfontSplitter logo

I have just released a new version of DfontSplitter for Mac. It is a bugfix-only release, containing a single fix for an issue that affected some non-English versions of Mac OS X.

New Features and Bugfixes

  • Fixed a bug where DfontSplitter would report valid files as not being in the correct format on some non-English versions of Mac OS X. File type detection is now done through uniform type identifiers, avoiding this issue.

Known Issues

  • Converting TTC files on Mac OS X Leopard (10.5) does sometimes run into problems, where the TTC splitting script can’t open the TTC file. The reason for this is currently unclear.
  • Moving TTF files that have been extracted from a .dfont over to Windows — please see this workaround.
  • Some Font Suitcase files may not contain TTF data that can be extracted.

Users of DfontSplitter for Mac should update their copy of the application by launching it, and choosing DfontSplitter > Check for Updates from the menu bar. Alternatively, you can always download a fresh copy from the DfontSplitter project page.

Re-enable Mail.app Plugins in 10.6.5, 10.6.7

'Brick' plugin icon

Since Snow Leopard, each new release of Mail.app (recently updated with 10.6.5 and now 10.6.7) and the Message.framework it depends on changes a ‘plugin compatibility’ UUID and suddenly breaks any plugins or extensions you have enabled in Mail.app. The developers of each extension have to update each and every one manually, and can’t do so before the new software from Apple is released.

If you can’t (be bothered to) wait for the updates from your plugin developers to arrive, however, and are confident that the plugin will work with the new version, you can hack said plugins and force them to be re-enabled inside Mail.app using the following method. Here I’ll be working with GrowlMail 1.1.2, but this should work for most Mail.app plugins.

A word of warning — not only does this involve editing the plugin’s files, which if you get it wrong could break that plugin and force you to download and install it again, it is possible that your plugin really isn’t compatible with the new version of Mail, in which case it could cause more serious problems. Back stuff up before trying this — you should be doing so anyway.

» Read the rest of this post…