There's two things necessary to use the new fonts: 1. The fonts. They're available in full flashes and separately with the package I linked. 2. A new gecko that looks for these new fonts. Gaia doesn't directly specify Fira, so the new Fira needs to be specified as default.
-Michael Wu ----- Original Message ----- > Hi Michael (and everyone on the list), > > Based on your information, and since we can't full-flash Flame (as of > yet, as it may result in RIL-related problems), if I want UX/VxD folks > to review my UX/VxD implementation that uses the new font assets on > Flame, I would need to instruct them to download the zip file and run > the shell script, right? > > Thanks ;) > - John Lu > > > 於 2014/7/1 下午9:51, Michael Wu 提到: > > 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 > > > > 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 > _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
