Lee Passey wrote:
Adding three lines to the template file adds complexity?
No, but soon you'll start and say things like: if we did this to the TEI file, the rendering thru CCS would be so much easier, etc. etc.
I would never suggest creating a TEI file with the assumption that it would be rendered in conjunction with some specific CSS file, or indeed assuming that it will have some specific rendering at all. I recommend creating TEI files that are both valid and correct with regard to the TEI spec and not be concerned at all about how it might be rendered.
You just proposed the exact opposite thing: to hard-code a set of CSS stylesheets into the file.
On the other hand, simple modifications which will enable other people and applications to select a rendering should be acceptable if it's not a hinderance to the primary goal of producing valid and correct TEI.
If anybody wants to view their TEI thru CSS they should apply their preferred stylesheet by hand. Some browsers let you select a user stylesheet. No need to pollute the TEI file with that.
I'm not terribly enamored with <divGen> tags, because it seems to rely on software that so far is largely unimplemented. _I_ wouldn't recommend its use, but it _is_ part of the spec...
You need not use them. If you want to code the toc by hand, feel free. But you get some goodies if you use divGen like a toc with correct page numbers in the pdf. And you don't have to jiggle hundreds of links. -- Marcello Perathoner webmaster@gutenberg.org