View Single Post
Old 09-16-2012, 05:07 PM   #2513
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
... Another small update? Yay?! Fonts v5.4.N!

It's mostly a bit of cleanup after the fixes of v5.3.N...

* Removed the browser workaround, turns out it's unnecessary now that we're doing stuff properly .
* Added the bci_new FT override (bci built without FT_CONFIG_OPTION_OLD_INTERNALS). It might be more performant, but it might also be less compatible, especially on older devices/fw.
* Use the proper fontconfig config file in older K3 FW (<= 3.3).

That means that, if asked, the browser will now correctly use an FT override, like the rest of the system, thus saving a few hundred KB of RAM .

(And removing a somewhat nasty, most definitely hackish, piece of code that I'm surprised turned out to be so robust xD).

I also had to compress the packages in RAR, instead of ZIP, to get them under MR's 20MB attachment limit.

Last edited by NiLuJe; 09-16-2012 at 05:13 PM.
NiLuJe is offline   Reply With Quote