|
If you're going to work exclusively in Sigil, use Code View. You'll then be in the same position as a user of the first word processors, where control codes, similar to HTML markup, had to be explicitly entered inline with the text. This would not be a ridiculous way to work, particularly for a book where layout was an integral part of the message. You have the advantage of the Preview Pane showing the result.
Clicking on the next xhtml file to view the next chapter isn't really such a big deal, is it?
For proof-reading (however the epub was constructed) I often make a copy of the epub file and open it in ADE on my second screen. It's good to see what another program makes of the epub code, and good to see line-wrap errors that may have been not apparent in Sigil. Errors can be immediately corrected in Sigil. (You have to display a copy file in ADE, otherwise saving an edit in Sigil will confuse and crash the same file open in ADE.)
Don't even consider this method unless you're comfortable in Code View. Really, don't use Sigil at all unless you're comfortable in Code View. Just write your book in your favourite WP program, whether it be WordPad, Word or anything inbetween; resist the temptation to use strings of space characters to control indents, centering etc. and throw it into Calibre for automatic conversion to epub. It'll come out just fine.
|