• The first page out to have the title of the work and the author(s). My preference is with a small (<316 x 316) 'book plate' or graphics. Set the mood doncha know.
  This should be followed by a 'page break' (<HR SIZE="0">)

• The second page should have extra-information regarding the edition, the person converting the work etc. One ought to provide the full statements regarding the copyright status of the work (i.e. the Gutenberg stuff etc.) at the END of the work...access provided by a link. Don't put too much stuff before the text!
  Once again a 'page break'.

• Now for the Table of Contents. Best done as an 'list'. These ought to be links to the appropriate chapter / verse etc.
  Once again a 'page break' after the TOC (which may be several screens depending upon font, orientation etc.)

• Chapter Headings probably ought to be <BIG> and <BOLD>.
  the 'Headings' (H1, H2 etc.) and probably not of much use at least at the current state of the Rocket eBook rendering engine, but they may be in the future. The use of italics in my opinion is debatable for general usage. Some fonts really er,..suck in italics.

• Each chapter/section ought to end not only with a 'page break' but ought to have a 'back to top/section' link. I am 'pro-graphic' in the way that the graphic is a link that is large enough for my stubby finger to hit.
  I have been changing my mind about this one. I think that breaks of the reading too much and that one can just set the shortcut to go to the first page with a page done to the TOC

• Footnotes should be linked to their appropriate spot at the end of chapters/sections. Each footnote probably ought to have its own link to return from whence you came.
  Footnotes should probably have a 'page break' before and after (all of) them.

• Paragraphs ought to in general for prose be formatted with
  <P ALIGN="JUSTIFY">
  I usually just paste
  </P><P ALIGN="JUSTIFY">
  on the blank lines.
  Or...
  search/replace ^^P with ^P</P><P ALIGN="JUSTIFY">^P (with NoteTab)

• it has brought to my attention that 'justify' makes the page take longer to render..I guess that I didn't notice until it was pointed out to me..I still prefer it over the ragged edge..I can read much faster that way

• I am thinking that paragraphs ought to have 2 non-breaking spaces in front of them for indents. 5 spaces is probably too much for a short line. I believe it is meaningful to have the indent to catch the eye.
  I have changed my mind on this one as well. Not necessary, using paragraph tags properly gives you a blank line which is enough of a cue.

• Watch out for those texts that come with hyphens dividing words at the ends of lines. You'll want to remove those for good wrapping.

• Er,...spell-check before you code it

• My mind was changed about,'I suppose a perfectly coded text would have 2 spaces after a period', The period is probably a stop enough with the one space.

• I have accidently learned that there seems to be a <BOLD> tag. I must have been in WordPerfect mode in my head, because I typed <BIG><B></B></BIG> in succession for a title/subtitle combo and they came out very different

• I have noticed that if you have a very short line that is 'justified', it doesn't s t r e t c h it out, it leaves it alone unless it is long enough to wrap; interestingly enough if it 'just fits' then you get two blank lines between paragraphs

• I have definitely noted that the RocketWriter really does compress most HTML formatted files 2:1

• I often need to Modufy-->LInes-->compress (in Notetab) to strip the extra lines

Any questions or comments may be directed to Sam McDonald