On 19/08/11 05:59, Martin Holmes wrote:
> 1. Refactor the XML markup to break the list into two, with some kind of
> connecting mechanism to handle numbering correctly in the case of an
> ordered list. I don't like this because I don't like markup to be driven
> by output constraints.
At the NZETC we have have an XSL in out TEI to HTML pipeline that
essentially does this at transformation time. It floats <pb>s up to an
appropriate level and splits list etc.
This avoids the need to for markup to be driven by output constraints
and enables you to change you policy around when / how to split things.
Note that in some cases the NZETC also wilfully generates bad HTML,
knowing that browsers can handle it. The best example I can think of is
our table handling in ePubs contravenes the standard.
Library Technology Services http://www.victoria.ac.nz/library/