Comments on: @font-face in the wild

By: graeme

graeme — Thu, 04 Feb 2010 23:25:32 +0000

is it just me or is this going to lead to some absolute web disasters?!?!?

By: Ajax website styles

Ajax website styles — Mon, 24 Aug 2009 04:59:47 +0000

hey man thats a nice trick to use the Font import from any other place thanks

By: JC John Sese Cuneta

JC John Sese Cuneta — Sat, 20 Jun 2009 08:35:24 +0000

@Robin: There’s a way to minimize the download, add this to your @font-face


unicode-range: U+1700-171F;

That’s what I understood from the manuals and what not about that bit. It will allow the browser to download only the specified unicode-range, this way the end-user doesn’t have to download the whole font.

But then, on second thought, CJK, or just the Chinese glyphs alone is in itself huge even without the non-CJK ranges. I guess in that case, the end-user should get his/her own copy of the font(s).

——————————
Anyway, here’s an online sample of @font-face using the Filipino Baybayin writing script -> http://laibcoms.asia/blog/xindao/general3/baybayin-typepad-fil-tglg

Use FF3.5 and Opera 10. I haven’t checked WebKit-browsers yet. IE on the other hand won’t work (ever, because they only want .EOT).

Fonts I used are downloadable free-of-charge ;)

By: Robin

Robin — Fri, 12 Dec 2008 06:35:57 +0000

@font-face is Not suitable for CJK language. Because CJK font always too big. download it is a nightmare for visitor.

By: Adrian Rodriguez

Adrian Rodriguez — Thu, 02 Oct 2008 12:16:00 +0000

So instead of creating images, we can now just import fonts from folders in our server?

By: JC John SESE-Cuneta

JC John SESE-Cuneta — Thu, 28 Aug 2008 10:00:43 +0000

Yah. Personally, I do not think EOT is a good choice for the spread of ‘Web Fonts’ (as W3C refers to it). I even see it as the anti-thesis of Web Fonts and standards.

By: Alex

Alex — Thu, 28 Aug 2008 05:32:52 +0000

That’s the idea, but it’s up to the browser to implement that check. And to support it, Firefox and Safari would need code to read in an EOT file and output a plain OpenType file, say bye-bye to any restrictions in the EOT file.

By: JC John SESE-Cuneta

JC John SESE-Cuneta — Tue, 26 Aug 2008 16:59:55 +0000

The reason why MSIE only want EOT is because the browser still has to download the font in its cache/temporary directory for it to render the font on the user’s end. Making your URL to be the only to use it will be useless.

That is where EOT comes in. It allows foundries and site authors to specify which URLs the font will be usable. So even if it resides in your cache/temporary dir, the font will be unsusable because the URL it requires is not the one accessing the font (but instead your application or own sitet).

At least that’s what I understood, I may be wrong.

By: Exec

Exec — Tue, 26 Aug 2008 05:53:12 +0000

It’s the client that needs the font file, not the server. It has to download the font file to be able to use it.

By: Alison

Alison — Tue, 26 Aug 2008 03:43:37 +0000

No I was talking more like stealing the font and using it in your designs without paying for it.

Well if you have a username and password for accessing it then perhaps you could make a script to access it via username and password within the php file. Like a database connection file?

Oh! well what if you did that. Put the font in a database with restricted access? Or would that just be too slow to load?