I end up with Sections, not Chapters.

[rosshalde]

I imported an Epub that was all one big file, essentially just text with no additional styling of chapters, etc. added.

I followed the directions for how to make a picture the chapter heading in the TOC. That worked.

I then followed the directions for how to split one file into more than one.
That worked as well.

Problems:
1) It is calling it sections and when iBook opens the file, there is no table of contents as it doesn't care about sections, it wants chapters. The TOC is there in SIGIL, but not in iWork...thoughts? I loaded another epub that I had already styled with chapters and it doesn't display those with sections in sigil in displays them as chapters. How do I make this work?

2) My file seems huge. I added 10 images. They are each only 100KB, but my exported Epub is 7MB. Why? When I opened a Sigil fresh and just loaded all 100 pics, the exported epub was just under 7MB....how is that possible?

[rosshalde]

ps. When pic is actually overflowing onto the next page as well. That doesn't make sense to me.

[rosshalde]

One more everyone. Only the pics that I labeled as those with chapter heading in the TOC are showing up in the exported Epub. They are all there is code/book view in Sigil, but fail to show up with I actually export as Epub. Any ideas or fixes?

[Toxaris]

You really, really need to give more examples of the code.

That being said, there is no difference in section or chapters. Sigil has no understanding of the concepts. It is just a name of the files. If you split your book into more files/chapters/sections (pick your favorite word), you need to regenerate the TOC (IIRC the third button from the right). Otherwise the links are wrong. Even iBooks should pick that up...

There can be various reasons why a file is so big. Under Tools there is an option called reports. There you can find out where the size is coming from. Also check the misc folder in the bookbrowser (left side).
Possible causes (there are more):
- added font files that are not subsetted or perhaps even used
- images larger than you think
- non-used images
- an object/file in the misc folder that is not used.

I have read about overflowing of pictures to the next page in iBooks before. You can search on the forum about that. It has something to do with the coding I believe and it is I believe an iBooks quirk.

Have you imported the images into Sigil or just referenced to it? You need to add the images into the ePUB.

[rosshalde]

Have you imported the images into Sigil or just referenced to it? You need to add the images into the ePUB.

How do I tell the difference?
I have 100 pics in the images folder of Sigil. I then get to the place that I want to insert the pic and I click add file, then double click my picture and it shows up in both code and in the book mode. Are you saying I have only referenced rather than added?

Here is an example of code that works with the picture being a chapter heading
<h1 style="text-align: center;" title="Little Rag Doll"><img alt="Misericordia Readers Primer_Page_016" src="../Images/Misericordia%20Readers%20Primer_Page_016.jpeg" /></h1>

Here is an example of code that is not working for me.
<p class="s1 s3">She called Baby Boy.</p><img alt="Misericordia Readers Primer_Page_017" src="../Images/Misericordia%20Readers%20Primer_Page_017.jpeg" />

[MickiTee]

Originally Posted by rosshalde

Have you imported the images into Sigil or just referenced to it? You need to add the images into the ePUB.

How do I tell the difference?

Any images included in the epub can be located under Images in the Book Browser. Also make sure that you only have a single copy of each image. If you've got duplicate images then decide which one to keep, edit the file name in all the <img> tags and then delete the duplicates.

Sigil provides an option on the Tools menu to Delete Unused Media Files. You can do the same for Unused Stylesheet Classes. This should help reduce the size of your epub

Originally Posted by rosshalde

Here is an example of code that works with the picture being a chapter heading
<h1 style="text-align: center;" title="Little Rag Doll"><img alt="Misericordia Readers Primer_Page_016" src="../Images/Misericordia%20Readers%20Primer_Page_016.jpeg" /></h1>

Here is an example of code that is not working for me.
<p class="s1 s3">She called Baby Boy.</p><img alt="Misericordia Readers Primer_Page_017" src="../Images/Misericordia%20Readers%20Primer_Page_017.jpeg" />

In your 2nd example, you need to move the closing tag </p> so that it is after the <img> tag as only classes used only apply to code/text between the start & close tags.

[Toxaris]

Items like images must be enclosed between paragraph, div, header or blockquote tags (there are more options, but not important now).
If you execute 'Check books' it would also have told you this.

[Notjohn]

Originally Posted by rosshalde

1) It is calling it sections and when iBook opens the file, there is no table of contents as it doesn't care about sections, it wants chapters.
2) My file seems huge. I added 10 images. They are each only 100KB, but my exported Epub is 7MB. Why? When I opened a Sigil fresh and just loaded all 100 pics, the exported epub was just under 7MB....how is that possible?

I routinely have 30 or 40 sections, since I put every image in its own section, sometimes with a caption, sometimes not. The TOC is built from headings, not from sections. I use H2 for chapter heads, though I assume H1 would also work. Use the TOC "tool" to generate your virtual TOC for advanced e-readers. You can also generate an actual, html TOC with that tool.

100 images at 100KB is 10 MB according to my calculations, but then I didn't major in math. (100 x 100KB = 10,000KB = 10MB, or have I lost my mind?

This is my image style:

div.image {
text-align:center;
margin-bottom: 0.25em;
}

For almost all images, I include width="100%" in the html pointer to the image, like this:

<div class="image" id="visitors"><img alt="something about the image" src="../Images/visitors600.jpg" width="100%"/></div>

Though that image was 600 pixels wide, I now go to 800 pixels if I can.

[Notjohn]

Ah, perhaps you had only 10 images. Right: that ought to have added 1MB.