A similar option is to have an HTML-rectification step, which processes
the invalid XHTML resulting from a "correct" transformation into valid 
(X)HTML (with lists split out from paragraphs, etc.).


On 8/18/2011 10:31 PM, Conal Christopher Tuohy wrote:
> Just to echo Stuart's comment below: this approach is always the one
> I favoured - it's a cross between Martin's options 1 and 2.
> It is like option 1 in that the TEI markup is refactored to split
> such lists into two, but unlike it in that the refactoring is not a
> manual process but automated. It's like option 2 in that it uses XSLT
> to automatically handle the case of lists with embedded formework and
> page breaks, but unlike it in that the special handling is performed
> entirely in TEI, independently of any transformation to HTML. This is
> done using a "pipeline" in which multiple XSLT transforms are chained
> together, with the output of one step feeding into the input of the
> next. To handle page breaks in list, you would use a transformation
> for which the input is TEI with lists containing page breaks, and the
> output is TEI in which any such lists have been split. So this is a
> preliminary, pre-processing step in which general TEI is converted
> into much more constrained TEI. This more constrained TEI is then fed
> into a stylesheet which converts it to HTML. Because the input to the
> HTML stylesheet is much s! impler TEI (without list//pb), the HTML
> stylesheet can be much simpler to write, understand, and debug.

Wendell Piez                            mailto:[log in to unmask]
Mulberry Technologies, Inc.      
17 West Jefferson Street                    Direct Phone: 301/315-9635
Suite 207                                          Phone: 301/315-9631
Rockville, MD  20850                                 Fax: 301/315-8285
   Mulberry Technologies: A Consultancy Specializing in SGML and XML