> On 22 Jan 2015, at 17:15, an <[email protected]> wrote: > > On Thursday, January 22, 2015 at 3:36:33 PM UTC+2, Chris Mills wrote: >>> On 22 Jan 2015, at 13:31, an <[email protected]> wrote: >>> >>> >>> There are 2 sides to this problem: >>> 1. >>> https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/ZTE_OPEN_C#System_images_from_Mozilla >>> points to flame-kk builds only and as I experienced it myself the font fix >>> doesn't help with those builds, the new fonts are just ignored. The >>> instructions should be updated, or Mozilla should provide flame images that >>> work with the instructions!! >> >> So do I need to update this to point to the jb builds instead? Sorry for >> being so out of the loop on this. > > If you ask me, that would be a very disappointing solution since the only > flame build non-kk is for 1.4 (stock is 1.3) and most people want to upgrade > to at least 2.0. The good people at Mozilla who are in charge of the builds > should provide flame-jb builds for 2.0, 2.1, etc. so that Open C owners can > benefit from those too.
I agree it’s not ideal. But I don’t know what other solutions we have out there right now. > >> >>> 2. I found 2 versions of the font fix, one incorporates the new fonts, the >>> other downloads them but they end up doing the same thing, flash the fonts >>> in /system/fonts. >> >> The most up to date instructions (on the flame page - >> https://developer.mozilla.org/en-US/Firefox_OS/Developer_phone_guide/Flame/Updating_your_Flame#Font_fix) >> show two different fixes. Which one should we recommend? Is ther any reason >> delete the inferior solution? Seems to me that this just creates unnecessary >> confusion. > > As I said, they both do the same thing, but fira-font-update.zip is self > contained. Right, yup. _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
