Plus, with Sigil, you can easily split at the page breaks or combine as needed. With ePub, you can make it look nice and when that's done, it will convert better. RTF in Word leaves a lot of garbage that you don't need and don't want. Then you can format it how you want it to look and convert it to AZW3. To be honest you are better to convert the PDF to ePub. Should I file a bug report? It seems like a bug to me My question is: the "insert blank lines in mobi when a page break in PDF is found" behavior is a bug or a feature? Since there is no images or such, it works well. What I do is convert the PDF to RTF, edit it and then convert from the edited RTF to mobi. The problem becomes annoying in a text that already contains some real soft scene breaks, as you can imagine, as the resulting MOBI will have a lot of fake soft scene breaks I certainly can use regex to fix this paragraph breaks, but I think that Calibre could handle these "PDF page break -> MOBI soft scene break" problem. However, if a paragraph is broken from one page to another in the PDF, no soft scene break is inserted, but rather a new paragraph begins in the point of the page break.
Playing around a bit, I've just found that this blank lines are soft scene breaks inserted by Calibre (if I use the option to "replace soft scene breaks" it become obvious). You can see in the resulting MOBI (using the internal viewer or even using Kindle itself) that there is some blank lines corresponding to every page break in the PDF file. Convert it with Calibre to MOBI, with all the options from Heuristics checked, and "Removing spacing between paragraphs" from "Look and Feel" checked too.
pdf book from Project Gutenberg (I got this ). Here are the steps I followed right now, just to be sure:ġ. And every PDF I've already tried to convert exhibit this problem, or I wouldn't cry for help. I've read the sticky many times in search of a solution.
0 kommentar(er)
