When designing a website, you have to be careful in only using fonts that your users will have installed on their computer right?

On my site, http://www.craigmoran.co.uk i like this font, but the only way in which i can use it is through an image.

Is there a way in which you can upload the ttf file to your site and link to it through there, or can this not be done??

Craig

I would say no, that it has to be done as a graphic as you said, but I too would be interested to hear about it if anyone else knows different.

there is a way.. Karinne had a topic about that, but I can't find it.

There is a script that renders your font into images, so everyone can read them.. or something.. KARINNE!.. HELP!

Oh, yes, yes, I remember now when you said Karinne - I found the thing she wrote and what she linked to was this:

http://www.mikeindustries.com/sifr

images or flash...

Hard decision!

Moved to Web Design in General



sIFR - I have used that in the past and it was great!

Depends what you want to use it for. It it's for titles that will never change like "About me!" on your about page or something, then I would just go with images. But if it's for article/blog titles, go the sIFR route

Thanks for that

Thought this might interest some of you

// Showcase: Superb Examples of Slick sIFR Typography

I still haven't had the need to use sIFR, but it has been in my bookmarks for a long long time. Out of curiosity, how does its loading/rendering time compare with that of around 10-20 PNGs/JPGs as title images?

I particularly like how sIFR titles can been selected and copied to the clipboard. If only the browsers themselves could manage such a feat when textual content in images is easily recognizable by the human eye.

I think it may be a tad slower because of the flash... depending on probably a variety of things but I'm not sure as I haven't tested.

I remember reading somewhere about this issue to some degree. Images are great to use for display, but unfortunately, search engines can't read it. This can be a bad thing because the image text usually is an important part of the markup (something the SE's would want to know about). Anyway, I remember a hack that work pretty nicely. Basically, using the image as a background for a div and, using css, still place the actual text (header element) in the markup but position it way off the screen (as opposed to display: none - not nearly as strong). This way, the markup is still there for the SE's and the image is still there for the beautification process.