On Thu, Oct 30, 2014 at 8:24 PM, Conal Tuohy <[log in to unmask]> wrote:
> My vote would be for (b) - to use <div> for pretty much everything, and to
> deal with typographical issues in CSS.
> I do sympathize with the desire to maximize the retention of TEI-encoded
> semantics, but these days I am less inclined to believe there is any
> significant payoff in doing so, and I think the additional complexity of the
> stylesheets is a barrier to modular reuse and a prohibitive cognitive burden
> for many people who might otherwise contribute to the stylesheets.
Is that a viable solution for ePubs read on epaper devices? I thought
there were pretty strong limits on what you could get away with in CSS
on such devices.
If we're doing everything in CSS, why go to HTML at all, why not
follow TEI Boilerplate
(http://dcl.slis.indiana.edu/teibp/content/demo.xml) and use TEI+CSS?