ID: embedded graphic

[dezignlady]

So if I open the ePub in Calibre and the linked TOC works there and it's visible then is it just an ADE thing?

[dezignlady]

ok I don't know what I did but after a little finessing of the file in Sigil and then opening again in ADE, all is wonderful again. arrrggghhh!

So a little more clean up and then the newbie needs to know what format do I need for Kindle? will do some searching on the forum and google as well.

[wannabee]

Duplicate entry

[wannabee]

Sigil breaks existing TOCS when I open an ePub with it.
I've used it when it didn't break the TOC but most of the time it does so I'd always work on a copy if you use it. I don't any more I use notepad++ to edit the exported files and have only very rarely needed to work on an Indesign created TOC/NCX file. They have always been fine. Duplicate TOC entries might be due to one of the tick box selections in the export/content window.

I don't export to kindle with the kindle exporter from ID. I convert the ePub to mobi in Calibre for the Kindle store. That way I only have to edit the one package. Amazon has accepted them OK. I think they'd accept an ePub and convert it themselves for that matter.

[charleski]

Originally Posted by wannabee

Sigil breaks existing TOCS when I open an ePub with it.

Sigil reconstructs the ToC by parsing the appropriate heading tags (<h1>, <h2>, etc) in the main text. If the chapter headers were constructed using <p> tags then they will get lost. It can be a bit of a pain, but it's hard to criticise since you should be using the heading tags to indicate logical headings in the document.

The one real benefit of InDesign 5.5 is that the paragraph styles used for chapter headings can now be linked to an appropriate heading tag so that it exports an ePub that's already properly tagged and won't run into these problems in Sigil.

[wannabee]

Originally Posted by charleski

but it's hard to criticise since you should be using the heading tags to indicate logical headings in the document.

I was criticized for this by our web designer. I use h1, h2 etc now. But I also have body-txt, body-txt-ctr, body-txt-it, body-txt-bld, body-txt-ind and tables. I'm not sure what Sigil would do to them so I haven't been game to use it.

[dezignlady]

Originally Posted by charleski

Sigil reconstructs the ToC by parsing the appropriate heading tags (<h1>, <h2>, etc) in the main text. If the chapter headers were constructed using <p> tags then they will get lost. It can be a bit of a pain, but it's hard to criticise since you should be using the heading tags to indicate logical headings in the document.

The one real benefit of InDesign 5.5 is that the paragraph styles used for chapter headings can now be linked to an appropriate heading tag so that it exports an ePub that's already properly tagged and won't run into these problems in Sigil.

Thanks. While I'm not quite into Programmer-mode when naming my style sheets all the chapter heads do have the same style sheets and are set to Level 1 in the TOC style used on Export.

I didn't use a copy so is there a way to ensure it's fine besides the fact that the Kindle previewer sees it fine, the mobi file is fine and the HTML files appear to be ok as I open them in Safari. I don't have an iPad to check the ePub on.

[JSWolf]

Originally Posted by dezignlady

Thanks. While I'm not quite into Programmer-mode when naming my style sheets all the chapter heads do have the same style sheets and are set to Level 1 in the TOC style used on Export.

I didn't use a copy so is there a way to ensure it's fine besides the fact that the Kindle previewer sees it fine, the mobi file is fine and the HTML files appear to be ok as I open them in Safari. I don't have an iPad to check the ePub on.

Do you have an iPod Touch or iPhone? They can also run iBooks.

[charleski]

Originally Posted by dezignlady

Thanks. While I'm not quite into Programmer-mode when naming my style sheets all the chapter heads do have the same style sheets and are set to Level 1 in the TOC style used on Export.

What you need to do is edit the style used for heading then go down to the 'Export Tagging' panel at the bottom of the list. Set the tag to h1 (or h2 etc for subdivisions) then type in a name to be used for the class (any name will do, though it's best to give it the same name (without spaces) as the style.

This will ensure that that style gets exported as a heading tag.

This only applies to CS5.5 BTW, it's the most useful change they made with the upgrade (apart from object instancing).