[Snooper]

Hi guys,
I need a little push with this one...
I'd like to use some non-standard font on my website, but I'm not sure how to do it correctly. It's always possible that something goes wrong when you mess with it. There's couple of things involved in it that I don't know answers, so I need help...

...mostly I'd like to know does my server (server22.000webhost.com) sends EOT and TTF font files as binary files, so they will be clear for all users, and if not how can I add .htaccess file with proper code inside to fix it...

...am I allowed to upload .htaccess file anyway, and way I can't find any on my server any more, I remember some time before, on my prior website, there was such files in the public_html folder?!

That will be enough for this time, I think. Thanks in advance... Bye.

S.

[drums]

Hi Snooper,

First of all, any custom font solution is currently not supported by all browsers, so you will have problems unless all of your users are using a particular browser type.

1) Yes - TTF and EOT should be served as binary files, however you can always force a particular mime-type for those files in htaccess using:

AddType application/x-font-ttf .ttf

The only problem is not all browsers will necessarily recognise this mimetype and know what to do.

2) Yes you can upload a .htaccess file. It may not be in your public_html directory already. In that case, you can upload one with any FTP client. If you have problems doing that, you can upload ".htaccess.txt" and then rename it to .htaccess using FTP or one of the File Managers in cpanel.

drums

[Snooper]

Thanx for advice drums,
I haven't idea of upload anything if not necessary. That's way I've asked does my server sends those font files as binary files. Now I believe it is, so no need to upload .htaccess to the server, right?!

When browsers matters it's supported by:
- IE4+ only .eot fonts,
- FF3.5+ .ttf .ott and woff
- Chrome 4.0 .ttf .otf
- Opera 10 .ttf .otf and svg
- Safari 3.1 .ttf .otf and svg
- Netscape 4 but discontinued by Netscape Navigator 6+

So, the only problem is this last one on the list. When IE matters .eot should be listed as first source file (before .ttf and others) in @font-face rule, and thing will work... also let's be honest, according to statistics 85% of surfers uses Firefox and IE.

thanx a lot,

S.

[drums]

Hi Snooper,

You're right about the majority of users being FF and IE. Chrome is gaining ground too, but as you say, @font-face works with Chrome using TTF and OTF. If you have problems with IE, you can always use some of the IE CSS kludges to create tags only IE will see.

It might not matter for you, but @font-face will break your CSS compliance and validation.

Good luck!

drums