Is the sIFR project dead?

I need to implement a typographic solution and am going to switch to the sIFR route, but sIFR 2 is ancient and sIFR 3 doesn't seem to work for a year and a half.

I've been looking into the method @font-face

, but I'm pretty sure the fonts I need to use do not allow web embedding.

+2


a source to share


5 answers


True, I got bored with development, busy with other things, and having the right web fonts became practically feasible. At the moment I don't see how I go back and improve sIFR, it just doesn't make sense.



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

+4


a source


Another alternative, simpler (imo): http://cufon.shoqolate.com/generate/ and is 100% JavaScript based.



+5


a source


Perhaps it really is "complete". Some projects just get to the point where there is nothing left to add because they fill their goals completely. This is very rare, but sIFR has a very brief purpose and there really isn't anything left to improve. There are 2 more projects that I know: MTASC and AMFPHP. Development stops because you have nothing to do if you don't want to change the nature of the project.

Greetz
back2dos

+4


a source


My guess is that with the advent of CSS3 fonts, it is no longer needed.

If licensing is your problem, I'm afraid sIFR has pretty similar issues like CSS3 fonts. I suggest checking out http://typekit.com for good web fonts.

+2


a source


Another interesting option, new from our friend Google: http://code.google.com/apis/webfonts/

+2


a source







All Articles