Quote:
Originally Posted by Education
Toxaris, you mention: "Once the ePUB is created, make any changes there". The issue is that I am not a html pro (I am just writing a book), but once I start editing directly in Sigil, it seems that it will soon require me to have a good working knowledge of html.
|
Take 10 and stop and look at the HTML side of one of your properly formatted chapters in Sigil.
Complicated? H no! English Grammar is way harder.
Messy code? Probably, if it came from word. (IMHO Messy is unnecessary style divisions: <p class="indented"><span class="none1"> , when the attributes from 'none1' could be combined into 'indented')
CSS is where the real style work gets done (avoid those styling buttons in Sigil) They generate in FILE SGC codes (but valid CSS coding if you need it).
copy (and but RENAME) a SGC# block to your stylesheet as a starter. RENAME the SGC code to something else Easy to remember. both on the
stylesheet and on the page (file) it came from.
SGC# code style assignments DO NOT span document files . The same code may do something entirely different in the next chapter (file).
Use Sigils 'Clip Editor' to create your own styling menu (and hid those similar buttons in Sigil: view: <remove the tick from the appropriate toolbar>.
Again, for
most cases, the CSS you will be using in the books body is
very basic (not like a WEB page, which uses the full range of CSS).
Don't know HOW (or have not decided) how to do a styleing, just assign and USE a separate stylesheet class for that block. eg.
will show up with the default look for now , you can fill in the STYLESHEET details later. All the places that were used will follow (the beauty of a single place style assignment) .
Your main job is to get the words all in their proper places (lines) on the page.
NB For years, Webscriptions (Baen) shipped e-books with a TOTAL of 40 lines of CSS code . Nothing fancy was ever done, just a Basic, simple book layout.