MobileRead Forums - View Single Post

Oxford-eBooks · 10-15-2012, 10:10 AM

QUOTE=DiapDealer;2208828]No clue, really. I do know that if you're side-loading a file you created with Kindlegen/Previewer, you're loading a dual-function, MOBI/KF8 hybrid file. When downloading a published ebook to those devices/apps, you're getting a stand-alone KF8 if the device/app supports KF8, and you're getting a stand-alone mobi if the device/app doesn't support KF8. Published ebooks are never delivered as dual-function hybrid files. They're either one or the other. So perhaps the Kindle apps on i(Pad|Phone) don't work perfectly with those side-loaded, dual format files? Just guessing of course—I don't have any iDevices to test on.[/QUOTE]
Hi DiapDealer - can I make sure that I've got this straight in my head. I'm having a problem with some media queries on a new project, which I think I've now solved. I tend not to use them unless I REALLY need to.

So, when KINDLEGEN (I use the command-line version V2.5) makes it's output, it makes a file with BOTH the old MOBI format AND the KF8 version together.
When sideloading, the device will pick one of these to render - it looks like Kindle V3.5 is showing KF8 by the formatting that it's picking up from the non-media query part of the CSS.

Kindle Previewer (Ver 2.51 is my weapon of choice right now) looks like it'll pick out the version depending on the device chose. Fire and Touch seem to render KF8 and Kindle and DX choose the MOBI.

I got myself a little confused earlier by making some classes with text colour to smoke out which styles that were working on various devices but the font colour wasn't changing on the MOBI version … I'm sure it used to?

Now, is it true that when, say the customer buys an eBook from Amazon, they serve up only the part that they need for their particular device?
Would that mean that if an eBook was uploaded in dual format BEFORE the new V3.5 was rolled out, that the customer at that time would only have the MOBI version, and their eBook wouldn't 'magically' start to render all the KF8 lovliness that someone buying the exact same eBook today would get?

I wonder if there's going to be any "how come this book looke different on my Kindle" questions?

10-15-2012, 10:10 AM	#27
Oxford-eBooks Zealot Posts: 138 Karma: 12096 Join Date: May 2010 Device: Loads!	QUOTE=DiapDealer;2208828]No clue, really. I do know that if you're side-loading a file you created with Kindlegen/Previewer, you're loading a dual-function, MOBI/KF8 hybrid file. When downloading a published ebook to those devices/apps, you're getting a stand-alone KF8 if the device/app supports KF8, and you're getting a stand-alone mobi if the device/app doesn't support KF8. Published ebooks are never delivered as dual-function hybrid files. They're either one or the other. So perhaps the Kindle apps on i(Pad\|Phone) don't work perfectly with those side-loaded, dual format files? Just guessing of course—I don't have any iDevices to test on.[/QUOTE] Hi DiapDealer - can I make sure that I've got this straight in my head. I'm having a problem with some media queries on a new project, which I think I've now solved. I tend not to use them unless I REALLY need to. So, when KINDLEGEN (I use the command-line version V2.5) makes it's output, it makes a file with BOTH the old MOBI format AND the KF8 version together. When sideloading, the device will pick one of these to render - it looks like Kindle V3.5 is showing KF8 by the formatting that it's picking up from the non-media query part of the CSS. Kindle Previewer (Ver 2.51 is my weapon of choice right now) looks like it'll pick out the version depending on the device chose. Fire and Touch seem to render KF8 and Kindle and DX choose the MOBI. I got myself a little confused earlier by making some classes with text colour to smoke out which styles that were working on various devices but the font colour wasn't changing on the MOBI version … I'm sure it used to? Now, is it true that when, say the customer buys an eBook from Amazon, they serve up only the part that they need for their particular device? Would that mean that if an eBook was uploaded in dual format BEFORE the new V3.5 was rolled out, that the customer at that time would only have the MOBI version, and their eBook wouldn't 'magically' start to render all the KF8 lovliness that someone buying the exact same eBook today would get? I wonder if there's going to be any "how come this book looke different on my Kindle" questions?