After merging all the .xml files, how do you divide it back into .xml files?

[automa]

I want to divide it by chapters now to make it more organized.

Would the loading take way too long on iPhone 5 if it is not divided into small segments?

[theducks]

Originally Posted by automa

I want to divide it by chapters now to make it more organized.

Would the loading take way too long on iPhone 5 if it is not divided into small segments?

Use the Sigil split Marker (Ctrl-Shift Enter: it is a HR with a special Sigil Class) at each point)
Once done: Tap F6 to make it happen
Save

[Toxaris]

Originally Posted by theducks

Use the Sigil split Marker (Ctrl-Shift Enter: it is a HR with a special Sigil Class) at each point)
Once done: Tap F6 to make it happen
Save

Ah, but before save regenerate the TOC...

[theducks]

Originally Posted by Toxaris

Ah, but before save regenerate the TOC...

The TOC is automagically kept in synch unless it contained relative links (ie #chapter_02). Flightcrew will holler in red about those

Moral: Always Validate after changes

[automa]

Originally Posted by theducks

Use the Sigil split Marker (Ctrl-Shift Enter: it is a HR with a special Sigil Class) at each point)
Once done: Tap F6 to make it happen
Save

Does that automatically divide the file by .xml files at the table of contents? Or Do I have to highlight the titles of table of contents individually and to Ctrl Shift Enter?

[theducks]

Originally Posted by automa

Does that automatically divide the file by .xml files at the table of contents? Or Do I have to highlight the titles of table of contents individually and to Ctrl Shift Enter?

You put the Mark in the FILE, not the TOC.
you should end up with something like:

<hr class=\"sigil_split_marker\" />
<h3 class="chapno">Chapter Title</h3>

If your Chapter headings were done the Sigil way, and a previous TOC (NCX) was generated, the references will be automatically updated.

You may need to regenerate an HTML (inline) TOC. Always Flightcrew after any change.

[automa]

Could you make a screenshot tutorial?/demonstration? Sorry I am having hard time understanding.

[theducks]

Originally Posted by automa

Could you make a screenshot tutorial?/demonstration? Sorry I am having hard time understanding.

How hard is it to place the cursor at the end of the line you want to split after, click once to set the insert point, tap ctrl-shift-enter?

At that point you should see a horizontal line (in book view) where the book will split.
If it is at the wrong place, delete the line. and try again.

Note 1: This only works at the end of a Paragraph or Div.
Note 1a: Books that use <br /> (break) to create a new line (really one massive paragraph) will not place the break anywhere close. If it is really wrong, you probably have one of these horrid documents and you will have to break the paragraph up by hand coding in code view.

When the lines appear correct, tap F6. the file will split at the markers (and the marker is auto removed)

Back up your book so you can recover.

Do not save if it is bad. On the Menu: File (pick the name from the recent list) <filename>: select DISCARD (trashes your errors ) when it asks what to do with what is showing and try again

[automa]

1. There is no problem in tapping F6 when you are not quite finished and then proceeding the process again right
2. Can a section be too small? I saw that the chapters are pretty small but the sections that are composed of multiple chapters are pretty large. In this case if I make a section for each chapter, would the file buffer each time it goes over to the next section or would it be okay because since each section would be small, it wouldn't take too much to load the next section?

[theducks]

Originally Posted by automa

1. There is no problem in tapping F6 when you are not quite finished and then proceeding the process again right
2. Can a section be too small? I saw that the chapters are pretty small but the sections that are composed of multiple chapters are pretty large. In this case if I make a section for each chapter, would the file buffer each time it goes over to the next section or would it be okay because since each section would be small, it wouldn't take too much to load the next section?

That is device dependent.
Big file have a very noticeable lag on my PEz.
Making Logical break points at the chapter makes it seem normal.
Not breaking on a small chapter now makes an inconsistency between chapters (assumes you still have a Pagebreak Before so a new chapter starts on a fresh screen)

[exaltedwombat]

Originally Posted by automa

1. There is no problem in tapping F6 when you are not quite finished and then proceeding the process again right
2. Can a section be too small? I saw that the chapters are pretty small but the sections that are composed of multiple chapters are pretty large. In this case if I make a section for each chapter, would the file buffer each time it goes over to the next section or would it be okay because since each section would be small, it wouldn't take too much to load the next section?

Start a new file where you want the reader to see a new page. These are conventionally called "chapters".

In the special case when a book has no obvious chapter divisions, split occasionally to help devices that choke on over-large files. You'll get a page break. Live with it.

If a chapter is short, that's fine. Ebook convention is to start a new chapter on a new page.