Quote:
Originally Posted by CalibUser
... it is easier to find these errors and directly join the errant paragraphs together using the Backspace key in Book view instead of using using code view where tags need to be deleted. Another example is where I look for split speeches - I find it easier to find these errors in Book view as opposed to Code view.
|
It is just as easy to find this using PV. When you are scrolling down the PV and find an error, click on it...it automagically moves the CV to the corresponding location. Being able to see which <tags> are being selected is actually a big plus...it keeps you from inadvertently forgetting to clear a tag, or worse yet, clearing too many tags!
Quote:
Originally Posted by CalibUser
I also tend to produce new books by typing directly into book view; and this makes it easier to put in new paragraphs by just pressing the Return key. I apply formatting using the styles (eg italics) in the toolbar. In my opinion, the Book view mode makes the text easier to write, check and edit without having to 'stumble' over tags.
|
I'm sorry. And I do mean it in the nicest possible way.
I would
highly recommend using a full-featured word processor to actually write your books. BV is not meant to do all the cool things that authors need when pouring their brains out onto "paper". Once you are "finished", then you can use any number of methods to import that chapter/book into Sigil for final cleaning.
There are very few tags that an author needs to know about
:
paragraph - <p></p>
emphasis (italics) - <em></em>
strong (bold) - <strong></strong>
headers (Chapter/Part) - <h1></h1> thru <h6></h6>
division (section or non-paragraph) - <div></div>
block quotes - <blockquote></blockquote>
special groups of characters - <span></span>
That's pretty much it. Learning how to style them using css is a "little" more involved. If you don't understand css then giving a professional a clean manuscript with just the above tags would make things MUCH faster/easier.
Cheers,