title: Why not use otf format in fontawesome to fix chrome bad rendering issue?
body: <p>Trying to find a way to get better antialiased rendering of fontawesome icons in chrome in windows i found that using 'otf' format solve the problem.</p>
  
  <p>i used in fontawesome.css:</p>
  
  <pre><code>src: url('../font/fontawesome.otf?v=3.1.0') format('opentype'), 
  url('../font/fontawesome-webfont.eot?#iefix&amp;v=3.1.0') format('embedded-opentype'), 
  url('../font/fontawesome-webfont.woff?v=3.1.0') format('woff'), 
  url('../font/fontawesome-webfont.ttf?v=3.1.0') format('truetype'), 
  url('../font/fontawesome-webfont.svg#fontawesomeregular?v=3.1.0') format('svg');
  </code></pre>
  
  <p>rendering is very good in chrome with a minor issue "in some icons the very top of the icon is cropped", other browsers render the icons clearly without any issue.</p>
  
  <p>my question, why otf version is not used in fontawesome to fix chrome bad rendering issue, the otf file is already present but not included in css?</p>