However, for the first paragraph, $HTMLFirstParagraphStart and $HTMLFirstParagraphEnd are used. The defaults may be set to the same as above but the mechanism allows for different first paragraph styling. For instance, a house writing style might be to indent all paragraphs save the one after a heading, and so on.
The default value for $HTMLIndentedParagraphStart is <code><blockquote></code>.
Quick lists. Adding markers at the start of a paragraph automatically trigger HTML lists (see more detail):
- An asterisk (*) or bullet (•) results in the paragraph exporting a <code><ul></code> bulleted list. Each successive paragraph with the same starting character is another list item in the same list.
- A hash symbol (#) results in the paragraph exporting an <code><ol></code> numbered list. Each successive paragraph with the same starting character is another list item in the same list.
Auto-headings. Increases in body text size of whole paragraphs causes ^text^ to export those paragraphs as headings. Thus:
- 2-3 points larger is exported to HTML as <code><h3></code>
- 4-5 points gives <code><h2></code>
- 6 or more points above body copy is exported as <code><h1></code>
Generally this is a useful enhancement but it can be problematic if the text size has been enlarged only for clarity within Tinderbox itself. If the intent is for all text in a note to be the same size, but just bigger than the norm, e.g. in a 'readme' note, set the $TextFontSize for the note to the same as the display size in the note window. As the text is now the base size (for that note) auto-headings are not invoked during HTML export.
Controlling auto-markup. All these automatic features are controlled via $HTMLMarkupText with ^text^ used to export $Text. If instead ^value($Text)^ or ^text(plain)^ are used to export $Text, the above effects are by-passed but there is no automatically generated HTML. In the latter case, the user would have to manually insert any desired HTML mark-up, e.g. paragraph tags, directly into the $Text.