InDesign to Calibre to ePub

[sperry1975]

I've used InDesign to create my ePub file which I checked on ebookflightdeck.com and discovered some errors. Here are two errors I need to correct and I'm wondering if Calibre can correct them or help me correct them?:

These files include inline styles.
OEBPS/cover.xhtml
Content and presentation should be separate in EPUB files. Inline styles are difficult to edit easily and are not the best approach. We recommend that you move all of your styles to an external stylesheet.

This EPUB contains content files over 300 KB in size. While there is no formal standard regarding individual file sizes, larger file sizes can slow down the loading and response time on older eBook devices. Also, some major devices in the marketplace use the Adobe RMSDK, and that display engine has a hard limit of 300 KB on all content files. Please consider breaking these files into multiple parts to keep them under this limit.
See this file: OEBPS/Diane's_Cookbook_EPUB_3.xhtml

[kovidgoyal]

If you want to correct those warnings automatically, run an EPUB to EPUB conversion in calibre. Otherwise use the editor to correct them manually. If you dont understand them, ask in the workshop or epub forums here for help.

[sperry1975]

Thank you for the reply. Unfortunately your suggestion to correct those warnings automatically by run an EPUB to EPUB conversion in calibre failed to produce the same quality eBook I have before then EPUB to EPUB conversion. The final product didn't have the cover image some of the initial pages where moved to a different location. Images were pixelated which were once fine and clear. If you ask me this program sucks.

[theducks]

Originally Posted by sperry1975

Thank you for the reply. Unfortunately your suggestion to correct those warnings automatically by run an EPUB to EPUB conversion in calibre failed to produce the same quality eBook I have before then EPUB to EPUB conversion. The final product didn't have the cover image some of the initial pages where moved to a different location. Images were pixelated which were once fine and clear. If you ask me this program sucks.

The operator did not bother learning his tools before turning them on.

Each one of your complaints was because of something you failed to control to prevent DEFAULTS from being used.
DEFAULTS are what the MAJORITY of users use.

Initial pages moved? Ore were the just pushed along to allow the DEFAULT "Cover and Jacket' to be inserted. Calibre only reorders when the original OPF was garbage, and can't be used.

[sperry1975]

Originally Posted by theducks

The operator did not bother learning his tools before turning them on.

Each one of your complaints was because of something you failed to control to prevent DEFAULTS from being used.
DEFAULTS are what the MAJORITY of users use.

Initial pages moved? Ore were the just pushed along to allow the DEFAULT "Cover and Jacket' to be inserted. Calibre only reorders when the original OPF was garbage, and can't be used.

I was under the impression that this was all an automatic process and everything wrong would be automatically corrected if I converted and ePub to ePub via calibre. I was apparently told wrong and there's a lot more to it than I was led to believe. I've managed to get into the file and edit the images adding good quality images, fixed some mis ordered items, but I still need to figure out how to get some formatting fixed in the TOC. Also I'm having significant problems with the "titlepage.xhtml" file. It's displaying a big question mark. I don't know how to correct that since the file it references "OEBPS/cover.xhtml" is working fine and displays the image it references fine, so I'm a bit puzzled how to fix this one.

[theducks]

Many viewer tolerate errors. Calibre tries to fix those so the Many, become MOST.

BUT, in this case conversions use (updates) the Latest Metadata (inc cover) from the Library. You don't seem to need/want that default

[sperry1975]

Originally Posted by theducks

Many viewer tolerate errors. Calibre tries to fix those so the Many, become MOST.

BUT, in this case conversions use (updates) the Latest Metadata (inc cover) from the Library. You don't seem to need/want that default

You say your willing to help if I'm willing to brainstorm correct? Well I'm brainstorming and have not yet figured out why the "titlepage.xhtml" will not display the image it's suppose to. I did change the referenced image file size from 600 x 800 to the actual size of the image hoping that would fix it but it didn't. At present I'm still working on the TOC text styles that appear fine in the ebook-editor preview window, but the actual file when exported as an ePub looks different like it's using justify instead of left align.

[sperry1975]

Well I've got about everything I can think of corrected or fixed except the "titlepage.xhtml" which will not display properly the image that is there. This one problem totally perplexes me.

[jhowell]

Originally Posted by sperry1975

Also I'm having significant problems with the "titlepage.xhtml" file. It's displaying a big question mark. I don't know how to correct that since the file it references "OEBPS/cover.xhtml" is working fine and displays the image it references fine, so I'm a bit puzzled how to fix this one.

This doesn't make sense. Are you trying to display cover.xhtml as an image from another xhtml file? You can't do that.

Perhaps you could post the code you are using for this.

[sperry1975]

Originally Posted by jhowell

This doesn't make sense. Are you trying to display cover.xhtml as an image from another xhtml file? You can't do that.

Perhaps you could post the code you are using for this.

Here's the original code generated by the program for that file:

<?xml version='1.0' encoding='utf-8'?>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
  <head>
    <meta name="calibre:cover" content="true"/>
    <title>Cover</title>
    <style type="text/css" title="override_css">
            @page {padding: 0pt; margin:0pt}
            body { text-align: center; padding:0pt; margin: 0pt; }
        </style>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/>
  </head>
  <body>
        <div>
            <svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" width="100%" height="100%" viewBox="0 0 600 800" preserveAspectRatio="none">
                <image width="600" height="800" xlink:href="OEBPS/cover.xhtml"/>
            </svg>
        </div>
    </body>
</html>

After doing some searching on the web I discovered a different line of code I can use that works, so it is possible:

<?xml version="1.0" encoding="utf-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
<style type="text/css">
/*<![CDATA[*/

body.sgc-1 {margin: 0px; text-align: center;}
/*]]>*/
</style>
</head>

<body class="sgc-1">
<div><img alt="" src=“Cover File.gif” /><img alt="Image" src="OEBPS/image/Cover%20File.gif" /></div>
</body>
</html>

[sperry1975]

After export I discovered a couple more problems. One is the the images I updated didn't end up getting updated. I think the problem is the program defaults to 72 dpi for all image exports. Therefore I need to find some way to correct that.

[BetterRed]

@sperry1975 -I've sort of lost track of where you're at with this. But to prevent image re-scaling in Conversion try setting Page Setup->Output Device to Tablet.

BR

[theducks]

Your second code exanple was from a old Sigil edit
.sgc-1 was the giveaway

BR pointed to the SIZE issue. Calibre uses the best size for the Device you declared (800x600 in this case).

[sperry1975]

Originally Posted by theducks

Your second code exanple was from a old Sigil edit
.sgc-1 was the giveaway

BR pointed to the SIZE issue. Calibre uses the best size for the Device you declared (800x600 in this case).

The trouble is I need it to export at no less than 150 dpi because any less degrades the image so much so that one can't make out what it says. Therefore if I export for a tablet device can the same ePub file then be used on an iPhone or equivalent?

[BetterRed]

As I understand it, IOS will scale images to the device it's running on, I would be flabbergasted if Android platforms didn't do the same. I suspect e-reader devices such as Kindle, Kobo and the boatload of other e-readers are more likely barf on images of wrong size/weight/density/genre etc.

BR