View Single Post
Old 02-06-2019, 09:31 AM   #8
shamanNS
Wizard
shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.shamanNS ought to be getting tired of karma fortunes by now.
 
Posts: 1,125
Karma: 12345678
Join Date: Feb 2010
Location: Serbia
Device: Kindle PW5, Kobo Libra 2, Kindle PW1
@NiLuJe: The KFX equivalent file is named "CONTENT_FONT_RAMP". But unlike "FONT_RAMP" parsing of that files is disabled on "stock" firmware.

People with jailbreak-ed Kindles can make one simple edit of appropriate JAR file to enabled the parsing / set "debug" flag to true. (the variable is still named "debug" on firmware 5.10.x, even though there was a new round of code obfuscation).

The best course of action would probably be for all of us to organize and "flood" kindle-feedback@amazon.com inbox with e-mails asking Lab123 team to just enable that parsing functionality in all future firmwares.

Last edited by shamanNS; 02-06-2019 at 02:35 PM.
shamanNS is offline   Reply With Quote