Quote:
Originally Posted by rashkae
Err, no, sending through the driver and converting to Kepub (in calibre) will not be the same. Converting within Calibre itself will send the the book through Calibre's whole e-book processing chain. With Default settings, that will make dramatic changes to the book, (and even with all the changes to default I make, there are still things that will get changed during the conversion process, such as font size variable, (small, medium, etc.) being converted to some predefined rem value, (or your custom em values, if you enable font size scaling, the default). Files will get split based on heuristic chanter splitting.. and I'm sure many many other changes I can't point at the top of my head.
|
Yes, a conversion will do a lot of other things. But, we were talking about what happens when there is a line feed in the middle of the text. And more specifically immediately after a close tag. I know that the calibre conversion doesn't remove line feeds like this. And the kepub conversion is an epub conversion followed by running the same code that add the spans as the extended driver uses, in all likelihood, the line feed will be lost after a conversion. Sure, there are some options in the conversion that would affect this, such as the unwrap lines, but, if the line feeds get through the epub part of the conversion, the kepubification step will trigger the same problem.
Quote:
|
Edit: I can not replicate the problem on Calibre 4.8 either way, however.
|
That doesn't surprise me to much. The driver and conversion use some of calibres routines for this. There were some changes in them earlier in the year that affected the driver and the conversion. This is probably related to those changes and no-one had a book with exactly this formatting to see the problem. Or it didn't worry them.