08-04-2011, 02:16 PM | #1 |
Member
Posts: 17
Karma: 112
Join Date: Feb 2011
Device: iPad, nook color, Kindle
|
KindleGen vs calibre
I'm wondering if anyone else has come up against differences when converting epub files to mobi. I'm finding that converting using KindleGen gives me a completely different file from what I get with calibre. KindleGen images are appearing much bigger and the navigational TOC is disabled. Files converted with calibre seem to convert much more cleanly...
Anyone else got an e-headache from this? |
08-04-2011, 02:54 PM | #2 |
Grand Sorcerer
Posts: 27,463
Karma: 192992430
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
ePubs converted with calibre come much closer to looking like the original epub I made than kindlegen seems to. But each day, I learn new ways to format my epubs so that kindlegen doesn't butcher it. Now, usually, I can make a couple of tweaks to the CSS in my source epub before I run it through kindlegen (if there isn't any crazy layouts involved) to produce the mobi. Anything so I don't have to maintain two completely separate projects for one book. I don't do a lot of graphic stuff--I'm basically only in it for the words--so I've found that the KISS method is crucial to my personal successes.
|
Advert | |
|
08-04-2011, 03:04 PM | #3 |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
I do it the other way around: I create a Mobi book and then convert that to ePub. That seems much less error-prone.
|
08-04-2011, 03:13 PM | #4 |
Guru
Posts: 688
Karma: 150000
Join Date: Feb 2010
Device: none
|
In my experience, I've found these differences:
Actually, for my own use I like the Calibre conversion somewhat better. But for commercial applications (Kindle store) I pretty much have to go with kindlegen starting with a "specially crafted" epub to get the results I want. Which is why I'm a little hazy on the details of Calibre conversions. |
08-04-2011, 03:39 PM | #5 | |
Grand Sorcerer
Posts: 27,463
Karma: 192992430
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
1) Converting the epub to mobi with calibre 2) unpacking that mobi with mobiunpack.py 3) recreating the toc.ncx and tweaking the opf file by hand (I also have a few automated scripts of my own to help) 4) feeding the opf file to kindlegen I get the look of the calibre conversion, but produced by kindlegen. |
|
Advert | |
|
08-04-2011, 09:50 PM | #6 |
Wizard
Posts: 1,613
Karma: 6718479
Join Date: Dec 2004
Location: Paradise (Key West, FL)
Device: Current:Surface Go & Kindle 3 - Retired: DellV8p, Clie UX50, ...
|
|
08-05-2011, 09:36 AM | #7 |
Member
Posts: 17
Karma: 112
Join Date: Feb 2011
Device: iPad, nook color, Kindle
|
I need to avoid maintaining separate files for each book. Because I am converting files created for print in InDesign, exporting a ePub is my first step. I should also note, I am Mac user.
So, how to edit a mobi file... I am going to try mobiunpack now, but what tweaks are needed for the ncx and opf files? And does only the opf file go into kindlegen? Any other mobi-editing info I should know? |
08-05-2011, 10:59 AM | #8 | ||
Grand Sorcerer
Posts: 27,463
Karma: 192992430
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
Quote:
The best thing I can suggest is to take a completed (and satisfactory) epub file and convert it to mobi with kindlegen. Then take the same epub and convert it to mobi with calibre. Using mobiunpack.py, unpack both mobi's and compare them to see what epub source produces what mobi code with each converter. It's all trial and error, but it's really the only way to learn. |
||
08-05-2011, 01:42 PM | #9 |
Member
Posts: 17
Karma: 112
Join Date: Feb 2011
Device: iPad, nook color, Kindle
|
Thanks DiapDealer. I appreciate your help.
I'm realizing how naive i was to assume that once a epub is buttoned up, converting to a mobi would be the easy part. How wrong I am |
08-05-2011, 02:07 PM | #10 |
Resident Curmudgeon
Posts: 73,645
Karma: 127837858
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
|
|
08-05-2011, 02:39 PM | #11 |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
No, it's not. Because Mobi is a simpler format than ePub, you can be a lot more certain that a Mobi file will convert cleanly to ePub than vice versa, and for the type of books I create, the capabilities of Mobi are sufficient for my needs.
|
08-09-2011, 02:46 AM | #12 |
Media Bloke
Posts: 2,381
Karma: 113956855
Join Date: Sep 2010
Location: NSW - Australia
Device: iOS
|
I also make ePubs from InDesign. Apart from some issues with tables they have converted OK in Calibre. I've had to rewrite tables as text when there are too many columns. They also have heaps of pictures.
|
08-10-2011, 01:35 PM | #13 |
Member
Posts: 17
Karma: 112
Join Date: Feb 2011
Device: iPad, nook color, Kindle
|
Yes, I am very happy with my calibre converted files. And luckily, I haven't had to deal with tables in my files. My hangnail is with the many images within my files. But I do think CS5.5 will heal many concerns nicely
|
08-29-2011, 06:03 AM | #14 |
Zealot
Posts: 107
Karma: 1000
Join Date: Sep 2010
Location: Melbourne, Australia
Device: iPad2, Kindle
|
Cripes. I have just done my first conversion from epub to mobi (using kindlegen, reading in Kindle app on iPad) and the results are somewhat alarming:
The front cover image is repeated on the second page There is no navigational TOC Justified text doesn't hyphenate Headings (aligned left in CSS) do hyphenate CSS working properly? Does Kindle treat H1, H2 etc in a default fashion? Or does it use the CSS? If the former, am I best to style all headings with P tags in order for Kindle to use my CSS? Lastly, and very worryingly, when I use the internal TOC (the toc on a page within the text) to navigate, the headings I've used as hyperlink destinations display incorrectly. i.e.: If I view the 'Chapter 1' heading by scrolling through the book, the heading style appears almost as I have designed it (perhaps a little larger than it does in the epub). BUT, if I use the TOC text links to navigate to that destination, the heading style applied to 'Chapter 1' has changed! It now appears much smaller than the CSS specifies. I haven't edited MOBI at all as yet. I was hoping Kindlegen would be a one step process but this looks like another learning curve. Are Amazon's auto conversions as unpredictable as all of this? Last edited by virtual_ink; 08-29-2011 at 06:10 AM. Reason: for clarity, i hope |
08-29-2011, 06:29 AM | #15 |
Evangelist
Posts: 448
Karma: 864744
Join Date: Mar 2011
Device: Kindle 3, LookBook, Nook Simple Touch
|
I guess I am odd, I create the book in notetab, the opf and the ncx then use kindlegen to create the mobi. making a epub then converting it to mobi seems an added step.
|
Tags |
kindlegen |
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Anyone using Kindlegen? | simonp | Kindle Formats | 11 | 09-16-2011 05:17 AM |
Troubleshooting TOC fails in Kindlegen 1.1, not Kindlegen 1.0 | cyberbaffled | Amazon Kindle | 3 | 12-25-2010 05:21 PM |
KindleGen 1.1 | pdurrant | Kindle Formats | 0 | 08-08-2010 06:18 AM |
Kindlegen now for Mac OS X (Intel) | pdurrant | Kindle Formats | 4 | 04-27-2010 02:46 PM |
Kindlegen vs Calibre: Which one compiles faster and is more efficient? | zdavatz | Calibre | 21 | 02-26-2010 02:57 AM |