If you compare trying to generate a font with something that works you could probably narrow the issue down.
I've seen this before in icon fonts and never had an issue but I haven't tested on Opera before either. I noticed when trying to re-generate the FontAwesome font from Font Forge I got validation errors with the em spacing and the glyphs had errors (self-intersecting, wrong direction, missing points at extrema). You could use a tool like Font Forge to check differences from other fonts. I would bet the glyphs are mapped to a different unicode area and maybe the browser doesn't read from there? I would compare the font that you said worked with FontAwesome to see what the differences are.
If you mention what font worked we could probably help out better. There are a couple different issues I would look into that I hope help you fix it. How I can detect if FontAwesome font is loaded? I'm tried to make a fallback using Modernizr "font-face" feature detection, but opera Mobile and BlackBerry 6 return true because they supports that-feacture. The problem is not just with my website, Font Awesome website examples and tests are not working. I tried with another server font with and works ok, but with FontAwesome I can't show icons properly. Opera mobile 10+ supports so the problem may be another. I tested with a BB Curve 9300, Modernizr and Google fonts and all is ok. (I don't know whats are the changes, but works)
Results: opera mobile now displays icons properly. I tried with two online font conversion tools.įirst I used to convert the original FontAwesome svg to ttf. I couldn't find any apparent problem, so I tried with unheard solutions. I'm using Bootstrap + Font Awesome, and all is ok with most desktop and mobile browsers, but Font awesome icons are not working with some browser like opera Mobile, Opera Mini, and some version of Android Browser.ĭoes anyone know that problem? and, Is there a solution ?
0 kommentar(er)
