I am sure this have been mentioned before in other discussions, but I can't find the answer. Do all the browsers today support the WOFF format?
I have found this info telling Opera Mini is the only browser that doesn't support those files
http://caniuse.com/#search=woff
Comments
But What Roel said.
I think it might be what @Jason Campbell said: The folks requesting those formats are not up to date with developments. It's a different question if, as font provider, you should be the one to educate them on that particular aspect of web technologies.
But things are changing fast. 6 months ago I wouldn't have thought of dropping EOT already. Now I don't think it will bug as many clients… probably sometime in 2017.
That's what we are thinking. It may be a bit of a forward-looking idea, but I'd rather be forward-looking than make it seem like we support technologies that were given up on quite a while ago, like EOT.
Personally I think that the Android issue is not so important, I'd think that there are more Windows users hanging onto old machines that might need EOT. And if I do get complaints from a customer, I would probably manually supply EOT rather than rock the boat.
So we have to make assumptions. Serving heavily optimised fonts to modern browsers who can handle them, and no fonts to obsolete browsers, is a very good start.
Dealing with FOUT and FOIT by having a good @font-face loading strategy is a much larger problem to be solved and not many web developers are doing that. They still believe including legacy formats in the old "bulletproof @font-face syntax" (published in 2009, when webfonts were still in their infancy!) is enough for an accessible, usable site. I think that's where the request of EOT, OTF/TTF and SVG versions comes from — because of outdated info, not because of a thorough research of the target audience and their needs.