EPUB output

[Roos]

Sometimes it happens to me that when i convert a epub to a epub (to insert a better/nicer cover or some such things) that the end result is a defevtive 0 Byte file :-(
Is it possible to let calibre check for integrity before replacing the 'old' file with a defective one?

Just another noob user ;-)

Wilco

[kovidgoyal]

Sure but you should track down what the underlying problem is. Try looking at the conversion log.

[kovidgoyal]

Originally Posted by dwanthny

The OP is talking about the resizing of the window of calibre's reader. As you resize the reader's window calibre does not maintain aspect ratio.

I had some time to look at this, it only happens if the img in question specifies a defined width of height either via css or the width/height attributes. I've added a workaround for this for the next release.

[oldbwl]

I have found a change in the conversion from RTF to EPUB (haven't checked RTF to other formats yet) since I upgraded to 0.7.30, an extra line is appearing for each Paragraph mark in the original RTF file. Just tried the older 0.7.29 version and it does not happen there.

[kovidgoyal]

Originally Posted by oldbwl

I have found a change in the conversion from RTF to EPUB (haven't checked RTF to other formats yet) since I upgraded to 0.7.30, an extra line is appearing for each Paragraph mark in the original RTF file. Just tried the older 0.7.29 version and it does not happen there.

yes that was intentional to preserve scene breaks implemented as empty paragraphs.

[oldbwl]

Originally Posted by kovidgoyal

yes that was intentional to preserve scene breaks implemented as empty paragraphs.

OK, but my converted output is now terrible.

My RTF documents are all formatted to follow the same appearence as this forum, which I find most pleasing and allows me to anchor my eye on the page, the gaps between paras adds relief and structure on the small screen IMHO.

Now I have to ensure that I take out one of every pair of ^p in a book before it is converted or Calibre will turn it in to ^p^p^p^p which looks stupid.

Why can't Calibre convert the RTF document to look exactly same when converted to epub. Why add the extra lines. Because that's exactly what it used to do until the fix for scenes.

I think you have solved a problem, but for me at least added a headache. I just want it to work the way it did, which was logical. I can't program so I can't make the change myself, can this be an optional tweak?

[kovidgoyal]

then I'd suggest sticking with 0.7.29, the changed behavior is a bug fix. calibre is now correctly converting the input RTF document. If you relied on the old behavior then stick with 0.7.29

[oldbwl]

OK, I get the message, but since the apearence has significantly changed then I feel it is valid to challenge your last assertion.

You have fixed one problem, sure, but created another. The original RTF document had ONE line between each paragraph. The Epub conversion used to have the same in 0.7.29. Now there are two lines between each paragraph after conversion. Two lines is one line unintended, and therefore it is NOT converting the layout as intended it to be.

Sorry Kovid. But I think you are wrong. If there is one line between each para before conversion then there should be only one afterwards. If I write a document and put spaces between paras, if I want to distribute the RTF doc as epub for others to enjoy, then to preserve my layout I now have to edit the spaces out before conversion. Truly that should not be necessary.

[kovidgoyal]

It may look like there is a single blank line between paragraphs in whatever program you are using to view RTF, but there is actually an empty paragraph. The two are very different and calibre now correctly distinguishes between them.

[Over]

I don't know if the problem is iBooks or the ePub conversion, but after 50 chapters or so, iBooks doesn't show any more chapters in it's internal TOC. And if I use the book's TOC, iBooks doesn't show how many pages are left in the current chapter. It shows how many remain 'til the end of the book.

I've tried to convert again, this time I saw the option that limits chapters to 50, but I think it was just a coincidence, because the problem remains.

What do you think might be the problem? And how could I fix it?

[kovidgoyal]

unfortunately, I don't use apple products, so I have no idea about iBooks. However, the first thing to check is open the book in calibre's viewer and make sure ass the links are there. calibre's viewer has no limitations on the number of entries in the TOC.

[Over]

With the Calibre's viewer, I've noticed that it added a TOC to the end of the book, with only 50 chapters (while the book's TOC at the beggining has all 99 chapters plus other entries (epilogue, etc)).

[kovidgoyal]

then you still have the max toc links setting applied. remember you have to change settings in the individual books conversion settings. changing the defaults wont affect a previously converted book.

[Over]

I've tried that, but with no success. I'm trying to convert from MOBI to EPUB, with Calibre's 0.7.30 version.

I've tried with another ebook, with success. So I guess the problem is the source mobi ebook, but I wonder what could be the problem...

I'm gonna try to convert to another format, and then to epub.

Edit: no success.

[oldbwl]

Originally Posted by kovidgoyal

It may look like there is a single blank line between paragraphs in whatever program you are using to view RTF, but there is actually an empty paragraph. The two are very different and calibre now correctly distinguishes between them.

I understand completely. BUT, Calibre is not converting in the manner you think, it is making 2 paragraphs not one. I think I must demonstrate exactly what I mean with a test example.

I attach a Test file in RTF, view this in any thing you like and observe the spacing - on my PC it appears as a single blank line between paras.

Convert that in Calibre to .txt format, see the spacing is preserved, but naturally the Justify and other formatting is lost.

Now convert in Calibre the RTF to epub, the spacing between para's is now far too big.

To really make the point convert the txt file to epub and the spacing is preserved. - I would do this but then the formatting is missing.