Do modern browsers still need a svg definition file for font-awesome?

My code is using the following:

@font-face {
  font-family: 'FontAwesome';
  src: url('../font/fontawesome-webfont.eot?v=3.2.1');
  src: url('../font/fontawesome-webfont.eot?#iefix&v=3.2.1') format('embedded-opentype'), url('../font/fontawesome-webfont.woff?v=3.2.1') format('woff'), url('../font/fontawesome-webfont.ttf?v=3.2.1') format('truetype'), url('../font/fontawesome-webfont.svg#fontawesomeregular?v=3.2.1') format('svg');
  font-weight: normal;
  font-style: normal;
}

Is it safe for me to assume that if I target IE9 and later that there will be no need for the svg or opentype ? The reason I am asking is because I notice the site that I use to make custom icons now comments out the svg.

//    url('@{FontAwesomePath}/fontawesome-webfont.svg#fontawesomeregular?v=3.0.1') format('svg');
//  src: url('@{FontAwesomePath}/FontAwesome.otf') format('opentype');

Answers


SVG was probably to support support for iOS < 5.0. Modern browsers only need WOFF.

See https://webmasters.stackexchange.com/questions/26992/if-i-have-only-woff-and-eot-what-browsers-am-i-supporting-with-font-face


Need Your Help

Python requests - Exception Type: ConnectionError - try: except does not work

python url python-requests connection python-2.x

I am using a webservice to retrieve some data but sometimes the url is not working and my site is not loading. Do you know how I can handle the following exception so there is no problem with the s...

Is REST a good solution if you have lots of requests?

web-services rest jboss arduino web-controls

I want people to controll my arduino robot via the internet. It's important that the controlling reacts very fast. The user may send many requests per second.