MobileRead Forums - View Single Post

NiLuJe · 12-16-2014, 05:56 PM

@hwhw: The fontconfig handling is unfortunately quite sucky in the legacy (FW 2/3/4x.x) version of the fonts hack, so it's fairly unwieldy to make it behave in another way than the very restrictive framework the hack allows, unlike the FW 5.x version, which gives much more freedom to the user to tweak the fontconfig settings

.

But yes, you're right, by default, the hack doesn't even touch Code2000, it just allows the user to tweak it

.

@geekyworld: In addition to that, which type of document are you checking that with? By default, KF8 files are *NOT* handled, enable the browser/KF8 handling through KUAL and restart the device.

12-16-2014, 05:56 PM	#17
NiLuJe BLAM! 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	@hwhw: The fontconfig handling is unfortunately quite sucky in the legacy (FW 2/3/4x.x) version of the fonts hack, so it's fairly unwieldy to make it behave in another way than the very restrictive framework the hack allows, unlike the FW 5.x version, which gives much more freedom to the user to tweak the fontconfig settings . But yes, you're right, by default, the hack doesn't even touch Code2000, it just allows the user to tweak it . @geekyworld: In addition to that, which type of document are you checking that with? By default, KF8 files are NOT handled, enable the browser/KF8 handling through KUAL and restart the device.