09-28-2012, 06:39 AM | #31 | ||
Grand Sorcerer
Posts: 27,903
Karma: 198500000
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
Quote:
|
||
09-28-2012, 09:08 AM | #32 |
Grand Sorcerer
Posts: 27,903
Karma: 198500000
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
It looks like Kindlegen is just carrying over the MOBI StartOffset from the first (MOBI) EXTH section and just appending it AND the KF8 StartOffset to the second (KF8) EXTH section.
That explains a lot. Including why it was "accidentally" correct sometimes—depending on the book. Last edited by DiapDealer; 09-28-2012 at 09:14 AM. |
Advert | |
|
09-28-2012, 10:59 AM | #33 | |
Grand Sorcerer
Posts: 5,635
Karma: 23191067
Join Date: Dec 2010
Device: Kindle PW2
|
Quote:
@NiLuJe Since you have a Kindle 5w (Touch?) and apparently nobody with a Kindle Fire has tested my combo file so far, can you please test the guide items in it? I'm curious whether this is strictly a K3 FW3.4 issue or whether other KF8-capable Kindles are effected by this issue as well. |
|
09-28-2012, 12:05 PM | #34 |
Connoisseur
Posts: 91
Karma: 22222
Join Date: Jul 2012
Device: Kindle
|
I meant that originally it was one file.
I split it into three xhtml files: the title, the toc and the main document. In that case the start was supposed to be the beginning of the third file. Both ways produced identical results. I have not generated anything with Calibre. |
09-28-2012, 12:07 PM | #35 |
Connoisseur
Posts: 91
Karma: 22222
Join Date: Jul 2012
Device: Kindle
|
If/when you understand the problem, please can you tell me how to work around it. Thanks.
|
Advert | |
|
09-28-2012, 12:08 PM | #36 | |
Grand Sorcerer
Posts: 27,903
Karma: 198500000
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
Yep. https://www.mobileread.com/forums/sho...d.php?t=183968 Certainly sounds like the same thing going on (no concrete evidence, of course). |
|
09-28-2012, 01:17 PM | #37 | |
Grand Sorcerer
Posts: 5,635
Karma: 23191067
Join Date: Dec 2010
Device: Kindle PW2
|
Quote:
Chances are that 99% of potential Kindle book readers will never even notice that there is a problem. Since the Go to Beginning guide item worked fine in a non-KF8 file created with an older KindleGen version and an azw3 file generated by Calibre, AFAIK, you only have two possibilities. a) Downgrade KindleGen to V1.1 build 99 and create a simple mobi7 file. This means that you won't be able to embed fonts and cannot use some other advanced features introduced with KF8. On the plus side your book is less likely to be rejected by Amazon. b) Use Calibre to create an .azw3 (=KF8-only) or a combo mobi file and keep your fingers crossed that Amazon won't notice that it wasn't created with KindleGen. Of course, you shouldn't discount the possibility that DiapDealer, NiLuJe or one of the other "usual suspects" will come up with a smart workaround or that a bored Amazon developer stumbles upon this thread and actually investigates and fixes this issue. Your encyclopedic knowledge of all things ebook related never ceases to amaze me! |
|
09-28-2012, 02:10 PM | #38 |
BLAM!
Posts: 13,492
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@DiapDealer: Ooh, you're right. It's carrying over the offset from the mobi7 part!
And I was wrong, AFAICT, the few KF8 files I've checked (straight from Amazon) only keep the correct one, so, yeah, maybe it gets 'fixed' after the KDP pass... That would imply that the 'split' action of MU should do the same . That said, I'll check how my Touch handles those master mobi, see if there's really an issue on the K3, even if what KG does isn't terribly smart in the first place. I'll try to come up with a less broken MU patch after checking all that . EDIT: FW 3.4 bug. It's working as intended on the Touch. Weeeee... -_-". Add that to the weird can't change font families bug in some KF8 files that uses multiple families for styling ... (Another thing happening on 3.4 that works flawlessly on the Touch). Last edited by NiLuJe; 09-28-2012 at 02:38 PM. |
09-28-2012, 02:54 PM | #39 | |
Grand Sorcerer
Posts: 27,903
Karma: 198500000
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
It'd be nice to be able to test/verify the "Go to Beginning" feature on an actual device before uploading to KDP, but that may not be in the cards. I can't, in good conscience, recommend altering the file that Kindlegen produces before uploading to KDP (which is frankly what it would probably take to "fix" at this point). There's simply no telling what could cause the modified file to be rejected by the KDP process. But a post-kindlegen script of some sort to deal with the double-offsets makes perfect sense to me -- for those who are creating ebooks with Kindlegen for personal use or for self-distribution. Perhaps, as NiluJe, recommended, as part of MobiUnpack's "splitter" feature. Last edited by DiapDealer; 09-28-2012 at 02:59 PM. |
|
09-28-2012, 03:31 PM | #40 |
Connoisseur
Posts: 91
Karma: 22222
Join Date: Jul 2012
Device: Kindle
|
But that would mean that we have a situation where a file made by Kindlegen is a correct input to KDP, and is a correct input to Previewer but is not a correct input to an actual device. Have I got that right?
If so, could we not have a patch that would somehow alter this mobi not for upload to KDP but only for upload to a device. If we can't do this I can't make files that will be correct on a device without uploading them and then buying them, which is madness. So I think you are then saying that Mobi-unpack could do it, but Mobi-unpack doesn't let one end up with a mobi file. Could Mobi-unpack produce the mobi7 and mobi8 versions of the mobi file for us as well as what it produces now?? Last edited by Tugger; 09-28-2012 at 03:34 PM. |
09-28-2012, 04:45 PM | #41 |
BLAM!
Posts: 13,492
Karma: 26047188
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
And here's a slightly less broken MU patch, that attempts to kill the extra StartOffsets in the mobi8 part when splitting (and tries to avoid the guide entries without title in mobi8 in a slightly less stupid way than my previous attempt)...
@Tugger: Keep in mind that (some) devices handle those (master mobis with multiple StartOffsets) files fine, not only the Previewer. It works correctly on my Touch. Only FW 3.4 (and possibly 4.1?) seem to be confused by these files. And with this patch, you can end up with a mobi7 & a mobi8 that should (hopefully) work as well as if they were processed by the KDP. EDIT: Updated patch in #53 Last edited by NiLuJe; 09-29-2012 at 02:06 PM. |
09-28-2012, 05:51 PM | #42 |
Connoisseur
Posts: 91
Karma: 22222
Join Date: Jul 2012
Device: Kindle
|
@NiLuJe That sounds great. But sorry for my ignorance, I don't understand how to make a mobi file (to send to a device) from the contents of the mobi7 (or mobi8) folders produced by Mobi-unpack?
(I only know how to modify the kindlegen source and drop the opf file onto Previewer to run Kindlegen again.) I also don't know how to make a new version of Mobi-unpack using your patch file. I'm a beginner at all this. |
09-28-2012, 07:08 PM | #43 | ||
Grand Sorcerer
Posts: 27,903
Karma: 198500000
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
Quote:
The stuff intended for sale for through KDP sounds like it will take care of itself. Last edited by DiapDealer; 09-28-2012 at 07:12 PM. |
||
09-28-2012, 08:09 PM | #44 | |
Bookmaker & Cat Slave
Posts: 11,482
Karma: 158448243
Join Date: Apr 2010
Location: Phoenix, AZ
Device: K2, iPad, KFire, PPW, Voyage, NookColor. 2 Droid, Oasis, Boox Note2
|
Quote:
We've been experimenting with this here, as well. It's our opinion that it's a K3 rendering engine issue. When we dl your test file, the "go to" on my Fire works. Of course, unfortunately, there wasn't really another page in front of it, as a viable test. It doesn't seem to work correctly on the K3. ETA: I mean to say, I do not believe it is a KG or KP issue. We have several books we've tested--they work fine on KP, on Fire and on K2, but the K3 can sometimes--not always--jump to the middle of the first page of Chapter 1 (or whatever page is set as the "text" location). I hope that this helps. (I would have replied sooner, but getting sideloaded files to finally SHOW UP on the Fire is a never-ending problem. It's very annoying. And, yes, I reboot and reboot, but for some reason, the delay time is frustrating as hell. Doesn't matter if I use wifi or USB.) Hitch Last edited by Hitch; 09-28-2012 at 08:12 PM. Reason: Added a clarification. |
|
09-29-2012, 02:57 AM | #45 | |
Connoisseur
Posts: 91
Karma: 22222
Join Date: Jul 2012
Device: Kindle
|
Quote:
What I don't know is exactly what I do in each case to take what is in the folder and put it on the device. I do not see a .mobi file to copy to it. The answer must be obvious, but not to me. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
How to define the "Start" or "Beginning" page in Calibre | paul_01 | Conversion | 5 | 08-12-2016 06:58 AM |
Kindle : go to beginning and default start location issues. | aschofield | Devices | 10 | 07-01-2012 02:10 PM |
Calibre wont start (first time start up) | Mike Railton | Devices | 15 | 05-25-2012 02:14 AM |
From the beginning ........ | Aspic8 | Writers' Corner | 15 | 10-10-2011 11:05 AM |
How do I go to the beginning of a book | heritage | Amazon Kindle | 8 | 12-24-2010 03:13 PM |