So Its May and I am writing about my April explortion so I guess posting late is my thing then.
Getting the Fonts a client wants to see into a webpage has been fraught with technical issues which tend towards the obscure from a clients point of view. From their perspective the graphics designer has created a document that they can see on a screen with no problem so why cant a web page do just that ? When these conversations raise their head these are the moments which lead a developer to beat their head against the brick wall of customer obstinacy as they attempt to explain why text embeded in graphics becomes problematic in terms of search, in terms of design and in terms of portability.
Google web fonts has been a good start in answering the how and the why as to the design issue but it has lacked a certain portability in terms of choices available to the designer. Cufon appears to fill the gap in the ‘pick your font and show it’ market but my experiences in the last few weeks demonstrate that the market for purchasing and implementing cufonts is tenuous and unsatisfactorily delivered.
Finally the End User License requirements of managing Fonts ( an aspect the copyright industry rarely seems to chase after as efficaciously as say Music or Video ) has been a constant source of delay and investigation and at the end of an hours deliberation over font texture and styles the lack of clarity on permission is a straw that breaks a back of a decision.
For now I am sticking with Google Fonts until such time as CuFon marketplace is mature enough to ensure simple delivery of Font content for a developer and webdesigner.
As for May; Well I want to take a detour back to Jquery and get a deeper appreciation of creating Ajax calls with live feedback such as the type required in status updates and scrolling completion status bars.
Thanks for reading.
2 Responses to “Say it in Style : Cufon or Google Fonts ?”
Leave a Reply