MobileRead Forums - View Single Post

NiLuJe · 03-12-2014, 10:32 PM

@mandy314: Amazon's setup is possibly more reliant on hardcoded stuff, I wouldn't trust it to actually do what FC asks.

That said, I can think of a few reasons for the difference in rendering though: whether the autohinter (and its various settings) is in use, or the bytecode. What exact snippet are you using for the second screenshot (and the first, for that matter)?

As for KOReader, I stopped trying to figure out how the hell the Cool Reader engine used FT, because, yeah, I get very surprising results there, and as I don't really use it, I never digged deeper. (It does use an internal copy of FT, so even in the best of cases (matching config, which you currently don't, since it doesn't care about FC IIRC), you'd never get the same rendering as Amazon's stuff anyway).

03-12-2014, 10:32 PM	#35
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	@mandy314: Amazon's setup is possibly more reliant on hardcoded stuff, I wouldn't trust it to actually do what FC asks. That said, I can think of a few reasons for the difference in rendering though: whether the autohinter (and its various settings) is in use, or the bytecode. What exact snippet are you using for the second screenshot (and the first, for that matter)? As for KOReader, I stopped trying to figure out how the hell the Cool Reader engine used FT, because, yeah, I get very surprising results there, and as I don't really use it, I never digged deeper. (It does use an internal copy of FT, so even in the best of cases (matching config, which you currently don't, since it doesn't care about FC IIRC), you'd never get the same rendering as Amazon's stuff anyway). Last edited by NiLuJe; 03-12-2014 at 10:38 PM.