otl and asciidoc comparison
===========================


headings
--------

Beneath each text type is otl version followed by asciidoc version.

<h1>    
	=====...                
	=====...

<h2>    
	-----...                
	-----...

<h3>    
	~~~~~...                
	~~~~~...

<h4>  
	^^^^^...          
	^^^^^...


indentation
------------

otl is capable of taking a cue from indentation when generating nested lists and even for regular markup.

For example, otl renders the following as an ordered list containing, at the second item, a nested, unordered list.

1. ordered list item 1
2. ordered list item 2
	- nested item 1
	- nested item 2
3. ordered list item 3



paragraphs
------------

Paragraphs are straightforward in otl. A carriage return is the end of the paragraph.
This is a new paragraph in otl but it isn't a new paragraph in asciidoc. Asciidoc looks for a carriage return followed by an empty line. More stuff in this second otl paragraph...

This is also a new paragraph in otl. More stuff in this paragraph...


text formatting
---------------

Beneath each text type is otl version followed by asciidoc version.

bold 
	**otl**
	*asciidoc*

italic 
	;;otl;; 
	'asciidoc' or _asciidoc_

monospace 
	[[otl monospace[[ or ++otl monospace++
	+asciidoc+ or `word`

small caps 
	unsupported in otl
	unsupported in asciidoc?

underline 
	__otl__
	unsupported in asciidoc?


passthroughs / verbatim
-----------------------

otl leaves HTML tags such as <b>bold</b> and <i>italic</i> untouched but asciidoc parses the tags

otl uses ## for passthroughs; asciidoc uses +++ for passthroughs

+++<pre>
This preformatted text should be untouched in asciidoc:
	1
	2
	3
</pre>
+++

##
<pre>
This preformatted text should be untouched in otl:
	1
	2
	3
</pre>
##