MobileRead Forums - View Single Post

NiLuJe · 01-13-2015, 06:13 PM

@jackie_w:

. I did mention that was something I cared deeply about ;p. Mostly I'm making use of what I learned when working on the Kindle hack

.

----

Hmm, that's... interesting. The codepath should be roughly identical on Calibre's side (the only thing that changes is the dimension used when rescaling), so my best guess would be nickel doing something stupid when the cover doesn't exactly match the device's resolution?

Meaning we should maybe also be doing the letter-boxing ourselves? >_<".

EDIT: I initially misread the code. If I follow, when Keep AR is enabled, the cover is uploaded as-is, which means nickel's in charge of scaling, which might explain the difference...

01-13-2015, 06:13 PM	#217
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	@jackie_w: . I did mention that was something I cared deeply about ;p. Mostly I'm making use of what I learned when working on the Kindle hack . ---- Hmm, that's... interesting. The codepath should be roughly identical on Calibre's side (the only thing that changes is the dimension used when rescaling), so my best guess would be nickel doing something stupid when the cover doesn't exactly match the device's resolution? Meaning we should maybe also be doing the letter-boxing ourselves? >_<". EDIT: I initially misread the code. If I follow, when Keep AR is enabled, the cover is uploaded as-is, which means nickel's in charge of scaling, which might explain the difference... Last edited by NiLuJe; 01-13-2015 at 09:05 PM.