====== Formats ======

* Write object to manage parse tree in DOM style
	* Hide parse tree behind method API.
	* Make this object suitable for use in template and make it interface to HyperTextBuffer.
	* Make this object automatically adapt headers when exporting.
	* get_parse_tree in HyperTextBuffer has some code to clean up trees
* Make it that formats do not need to know page object, do logic in parent class ? 

* Parsetree nodes for items in a list
* Serialize parse tree ?
* Style difference for non-existing links, external links etc. (both in GUI and in Export)
* Some way to embed raw HTML in a page that filters through to the html output
* different formats
	* pod - add perldoc plugin to documentation repository
	* XML - no transparent source format - parse '''<''' to ''&lt;''
		* use subset of HTML tags
	* latex
	* proof of concept dokuwiki support

* more native formats (pod, kwiki, ...)
* more import/export formats (latex, docbook, oo.org, ..)

* Wiki code for sub-/super-script ?

===== Zim Wiki format =====

Changes for our 1.0 wiki format.

The 1.0 format will have mail header style headers. One of these headers (the first) will specify the syntax used. Thus we can painless mix 1.0 and 0.0 syntax in the same notebook.

Also add headers for [[CreationDate]] and [[ModificationDate]].

==== Verbatim ====

Using indent as part of syntax was bad idea

* It does not allow to indent non-verbatim paragraphs, e.g. quotes
* It does not allow indent images, e.g. equations
* Skipped lines in lists screw up formatting

Solution: use block marker for verbatim paragraphs:

	'''
	This is a verbatim paragraph
	'''

Maybe we add other blocks later, like

	"""
	This is a quote, rendered italic
		-- A.U. Thor
	"""

etc.

==== Extensions ====

Codes for upper, lower etc. and extensions ?
