It is alwys best to output valid XHTML that way you can be sure that the
rest of the pipeline will parse the html correctly, but the pipeline is
perfectly capable of handling tag soup.
If you identify headers and footers, I suggest removing them entirely,
they have no place in ebook formats.
If you want to specify a page break in HTML, simply use the standard CSS
page-break-before/after properties.
It is alwys best to output valid XHTML that way you can be sure that the
rest of the pipeline will parse the html correctly, but the pipeline is
perfectly capable of handling tag soup.
If you identify headers and footers, I suggest removing them entirely,
they have no place in ebook formats.
If you want to specify a page break in HTML, simply use the standard CSS before/ after properties.
page-break-