What Are Cons to Use Cufon? Is Sifr Still Good Option? @Font-Face Doesn't Make The Letters Smooth Like They Look with Cufon or Sifr

Is there any cons to use @font-face?

You can use @font-face with:

  • Firefox 3.5
  • Safari 3.2
  • Chrome 4.0
  • Opera 10.5
    http://a.deveria.com/caniuse/#feat=fontface

For IE, the fallback is working great, but be sure to use the little hack for smooth rendering:
http://allcreatives.net/2009/12/05/smoother-font-face-embedding-in-ie-7-8/

Issues :

  • Font rendering quality differs from browser to browsers. As anti aliasing techniques of each browser are different :
    http://www.position-absolute.com/articles/html5-font-face-is-not-as-ready-as-you-would-think/
    Typekit will provide an online tool for that :
    http://typophile.com/node/65656
    typophile
    (source: typophile.com)

  • while the font is downloading, the user see the default font during 1 or 2 seconds

  • If the font is provided by your client, He may be concerned by the fact that the font will be downlodable from the website.
  • I've made printing font-face tests : it is just not working (but with sFIR it's ok)

Is the sIFR project dead?

Truth is, I got bored with development, got busy with other things, and proper web fonts started becoming feasible. At this point I can't see myself going back and improving sIFR, there's just no point to it.

The reason it was never officially completed is that there was still work left to do, albeit not very critical work. However to make r436 official 19 months after the fact would be a bit silly.

for site which language is chinese what should i choose @font-face or sIFR for custom fonts?

Personally I'd avoid font embedding for Chinese. The fonts are just so big, it's a lot to download. And there are more potential issues with different anti-aliasing modes: many CJK fonts are likely to render horribly with anti-aliasing off, and the default horizontal-only anti-aliasing of ClearType applies poorly to ideographs that weren't specifically designed for it, as they tend to have many near-horizontal lines (which Latin typically doesn't).

So I'd go with the image replacement for now.

The charset for any modern web application should be UTF-8. There may still occasionally be a need to encode to a legacy DBCS such as GB (maybe for sending mail to old mobile phones or some broken webmail services), but database content and normal web page serving should all be UTF-8.

how to use @font-face for supported browser and Cufon for the others

If you don't care about the SVG format support, LOFFS is a perfect solution for you.

Which font types i will need in @face-font and how to to make font smoother in all browser like sIFR?

You're using font-squirrel, so you should be uploading an OpenType font. You can also upload a TTF SVG you can untick as that's for iPhone support. Depending on the kerning, you may want to add:

filter: progid:DXImageTransform.Microsoft.AlphaImageLoader(src=UserSubmitted/fonts/hIEfix.png,sizingMethod=crop); zoom:1;

to your CSS declaration for the place you're using the font to enable/disable cleartype rendering, which makes some PC fonts look great and some look awful, depending on the individual font's hinting.

You should also be using the bulletproof (smiley varient) css invocation for best results and healthy syntax-based approach.



Related Topics



Leave a reply



Submit