mountbatt

This Plugin makes it totally easy to implement Cufon into your WordPress Blog. 
The only thing you have to do is converting your fontfiles and upload them into the plugins font directory. 
You can enable the objects you want to get replaced in the Admin Menu of your WordPress Blog.
History: 
1.6.10: 
– bug fix. sorry again. should sleep a bit more 🙂 
– now its back like it was at 1.6.8 – will fix the underscore bug later.
1.6.9: 
– a font name with an underscore is now recognised (thanks micky!) 
– for your security: backup your replacement code before updating!
1.6.8: 
– fixed save-bug! sorry!
1.6.7: 
– Bugfixes (thanks Curtis McHale!) 
– ie9 now supported
1.6.6: 
– Bugfix: <? changed to <?php – now it should work on servers that only allow php-scripts with the <?php call.
1.6.5: 
– some major changes done! the firefox error “9” is fixed – and now you can set the positions where the plugin loads in your template!
1.6.4: 
– bugfix for wordpress 3.0(b) to get the plugin back to work. (+ some infos added for working with fontnames) (thanks tomas!)
1.6.3: 
– font names with a dash are now matched (thanks Michael!)
1.6.2: 
– small changes 
– added a new hint in “FAQ”
1.6.1: 
– Sorry. My fault. I did something wrong during uploading to the WordPress Repository. Im new to this. So now comes version 1.6.1
1.6: 
– With great feedback from <a href="http://www.aldosoft.com" rel="nofollow ugc">Michael A. Alderete</a> now we are able to use WP-Cufon in different directories than the standard /wp-content/plugins/ – thats great. The plugin now also looks for your WP_CONTENT_DIR in wp-config. 
– now you can set a font with Cufon.set(‘fontFamily’, ‘Your Font Name’) 
– updated to the latest cufon-yui.js (v1.02)
1.5: 
– Changed: Now the plugin only loads the needed fonts that are entered by your replacement scripts (for this you have to enter the exact fontFamily names!) (Thanks John!) 
– Added: Font-Directory. To keep your own files wp-cufon now uses an external font-folder! check the “installation” page. 
– Added: WordPress 2.8.1 compatibility 
– Changed: now with compressed cufon-yui.js 
– Added: “Delay Fix”-Option to hack the delay on some websites. (beta) 
– Still ToDo: Fix the PlugIn to work with WordPress installations in own subdirectories. (Help needed!)
1.4: 
– Updated to the latest cufon.js (still uncompressed) 
– but the important thing now: i deleted the linotype frutiger fontfile 
– PLEASE DELETE THE Frutiger_LT_Std.font.js – We/You dont have any license for that!!! 
– now wp-cufon comes with the nice freefont “Vegur” (regular & bold) 
– i have to say sorry to you and sorry to linotype!
1.3.1: 
– Updated cufon to the latest changes from sorccu 
– e.g. line-heigt fix for ie6/7 and much more
1.3: 
– Fixed a bug: on some server it was impossible to save changes 
– Added a checkbox to enable jQuery (it works in non conflict mode, only if necessary!) – now you can use #selector in your cufon scripts. 
– updated to newest cufon-yui.js
1.2: 
– New cufon-yui.js – the developer added kerning! yeah. You need to re-render your fontfiles with the <a href="http://cufon.shoqolate.com/generate/" rel="nofollow ugc">generator</a>.
1.1.2: 
– Added JavaScript function for better InternetExplorer compatibility (important!)
1.1.1: 
– Fixed first value (stripslashes) (thanks Ryan!)
1.1: 
– Bugfix 
– added first (h1) value
1.0: 
Initial Release

WP-Cufon

Simple Plugin to enable Cufon fontreplacement

Jupitercow

0.6.8.1 Adds some much-needed functionality. It is now recommended that you move your fonts folder into your theme so that the fonts won’t be overwritten when you upgrade. It also fixes a 0.6.8 problem with the header reference to the SWF files when you store them in your theme.
0.6.6 Fixed a small change that caused some servers to stop working. If things stopped working for you, please upgrade to the latest version.
Important Upgrade Information
If you use WordPress’ built-in upgrade system, it will delete your fonts, unless you move your fonts folder into your theme instead. WP sIFR will automatically see the new location and no settings should be lost. If you do overwrite the fonts, your settings will be deleted the next time you visit the settings page. If you accidentally delete your fonts, replace them before going to the settings page. This is one of our main concerns for the next version.
WP sIFR
WP sIFR was created to remove the complications from getting custom fonts on a WordPress site. With WP sIFR, you only have to upload your SWF font file to the plugin directory and then login, activate it, and configure its styles all in the Settings panel.
WP sIFR benefits
<ul>
<li>Works on subpages</li>
<li>Simple backend code and setup</li>
<li>No customization necessary outside of WordPress Admin</li>
<li>New fonts working on your site in under five minutes</li>
<li>Protection against Adblock on Macs using Firefox 3 (text is still shown)</li>
</ul>
Font Settings and Deletion
Currently, to simplify font addition and removal, WP sIFR removes all settings for the removed font when you delete it from the fonts folder. This is permanent. The addition and removal script runs on plugin activation and when the Settings Panel page is visited. Be careful deleting fonts, or you could lose your settings. This will change in the next major release.
Firefox on Macs and Adblock
WP sIFR has the ability to detect against Macs using Firefox 3 with an Adblock add-on. If it detects this configuration, it will disable sIFR on your site for that user. This means that your text will still be shown, but it will not be sIFR text, like when a user has javascript disabled. It will not interfere with other Mac users who are not using FF3 or are using FF3 without Adblock.
<h3>Future Features</h3>
Number one priority from here is to save settings for all fonts even if the file gets deleted, and allow the user to delete a font that no longer exists.
Number two is to allow users to add multiple selectors that can be styled seperately!

WP sIFR

WP sIFR makes any font possible in your Wordpress installation in under five minutes.

WP-Cufon vs WP sIFR