On 11 Aug 2014, at 10:05, Frederik Braun <[email protected]> wrote:
> On 11.08.2014 10:45, Jan Jongboom wrote: >> I've seen this a couple of times, and now I see it also in some issue in bz. >> >> https://bugzilla.mozilla.org/attachment.cgi?id=8466079 >> >> What's this weird monospace font? It's somewhere in Gecko, because flashing >> a fresh Gaia on an affected build doesn't help. > > > This has been raised previously in this list with the subject "Fira > 3.109 has landed - Manual update required for shallow flashing", from > Michael Wu. > I will quote below: > > On 01.07.2014 15:51, Michael Wu wrote: >> Hi, >> >> We now have a new version of Fira Sans and Fira Mono. >> >> Unfortunately, the name of the font has changed again (Fira Sans OT -> > Fira Sans), and gecko will require fonts bearing the new name. If you > use shallow flashing or get automatic updates, you'll need to manually > add the new fonts in at the moment. >> >> I've put together a package with the fonts and a script to install the > font on the device. https://people.mozilla.org/~mwu/fira-font-update.zip This is covered in the Flame main page at https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame#Font_fix >> >> Run the script to push the new fonts on your device. adb probably > needs to be in your path if you're not running Linux. >> >> This can also be done without the script - >> adb remount >> adb push fonts /system/fonts >> >> These fonts can coexist with the old Fira fonts, so switching between > different gecko branches isn't an issue. >> >> Thanks, >> -Michael Wu > _______________________________________________ > dev-b2g mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-b2g _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
