Quote:
Originally Posted by blackest
Yes and no there are some aspects which are better than others for each chapter there are classes created and unfortunately they are not the same classes between chapters. However the find and replace can be quite useful once you have identified which class is being used for what e.g s1 might be chapter heading so you can replace s1 with say ch or something of course in the next chapter s1 might be body text but then you do a find and replace for that.
If I write in Sigil it isn't going to set classes for me at best I have the 6 H tags and P I see no way of automatically adding say <P class="caption"> any text will be <p> by default and it's going to be pretty tiresome to rewrite each and every <p> tag. At least with ibook creating <p class="s5"> i can search and replace <p class="s5"> with <p class="caption">
I may be missing something in Sigil that will make things easier. |
The headers in Sigil for the chapter titles will be the same based on which h you click in the toolbar. As for <p>, you want that because most <p> will be the same and you define p in the CSS as what p is most used for. You can then add in the classes for p when you need to change p. It's very simple really. You can make sure your eBook's code is compact. The way to do it is to keep the code as simple as possible. Most eBooks will work with very simple code.
Working in pages creates a mess that you then have to work to fix and fixing the mess can (more times than not it will be more work) be more work than working in Sigil from the start.