Comments on: Custom Fonts in WordPress with Cufon http://www.richardshepherd.com/custom-fonts-in-wordpress-with-cufon/ Making the web. Better looking. Thu, 26 Aug 2010 14:28:10 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Naushad http://www.richardshepherd.com/custom-fonts-in-wordpress-with-cufon/comment-page-1/#comment-344 Naushad Mon, 16 Aug 2010 05:34:26 +0000 http://www.richardshepherd.com/?p=1100#comment-344 Thanks Richard, your post really helped a Lot. :P Thanks Richard, your post really helped a Lot. :P

]]> By: steve http://www.richardshepherd.com/custom-fonts-in-wordpress-with-cufon/comment-page-1/#comment-343 steve Tue, 10 Aug 2010 08:31:43 +0000 http://www.richardshepherd.com/?p=1100#comment-343 Thanks for this, I found it really helpful! Thanks for this, I found it really helpful!

]]> By: richardshepherd http://www.richardshepherd.com/custom-fonts-in-wordpress-with-cufon/comment-page-1/#comment-326 richardshepherd Fri, 04 Jun 2010 17:33:54 +0000 http://www.richardshepherd.com/?p=1100#comment-326 I don't think Cufon is a joke, especially for all those users who have older browsers and can't render @font-face. I'm sure I read somewhere that the creator of Cufon saw it as a bridge until there was full cross-browser support for @font-face, and I think that's a fair summary. The stats on the sites I work on clearly show that we're not there yet, and I see Cufon as a real world solution. Cufon does arguably render a lot nicer too. That said, I'm not here to prescribe a solution to anyone. I use @font-face and sometimes I still use Cufon. I like TypeKit and the new Google Fonts API is also interesting. They're also significantly easier to use than @font-face (both from a code and liscensing point of view - getting fonts ready for IE can be difficult, especially for newer designers). Thanks for your thoughts - I don't disagree, but I also don't think it's as simple as @font-face or nothing. Yet. I don’t think Cufon is a joke, especially for all those users who have older browsers and can’t render @font-face. I’m sure I read somewhere that the creator of Cufon saw it as a bridge until there was full cross-browser support for @font-face, and I think that’s a fair summary.

The stats on the sites I work on clearly show that we’re not there yet, and I see Cufon as a real world solution. Cufon does arguably render a lot nicer too.

That said, I’m not here to prescribe a solution to anyone. I use @font-face and sometimes I still use Cufon. I like TypeKit and the new Google Fonts API is also interesting. They’re also significantly easier to use than @font-face (both from a code and liscensing point of view – getting fonts ready for IE can be difficult, especially for newer designers).

Thanks for your thoughts – I don’t disagree, but I also don’t think it’s as simple as @font-face or nothing. Yet.

]]> By: Eric Marden http://www.richardshepherd.com/custom-fonts-in-wordpress-with-cufon/comment-page-1/#comment-325 Eric Marden Fri, 04 Jun 2010 16:11:51 +0000 http://www.richardshepherd.com/?p=1100#comment-325 You're going to postpone looking at the only standard based way of doing it and instead focus 500+ words on a technique that was panned as soon as soon as it was released? Cufon is a joke, as was sIFR before it. You're better off using @font-face or going with out. You’re going to postpone looking at the only standard based way of doing it and instead focus 500+ words on a technique that was panned as soon as soon as it was released? Cufon is a joke, as was sIFR before it. You’re better off using @font-face or going with out.

]]>