On 26/01/16 11:25, Lou Burnard wrote:
I agree that it's really not satisfactory to have numbering down to 5 levels, and I did try this as a new 22.4.5, but that makes a mess of the current organisation of the chapter. The procmod stuff ought to be a sibling of what are currently 22.4.4.1 and 22.4.4.2, since these sections all describe children of elementSpec. I will have another crack at organizing things better. Yes. You have a better sense of elsewhere in the guidelines where we do this but it seemed weird to me (especially since procmod has so many of its own sections). I'll have a look at what you've done later.
Yes, "In the present implementation" was just wiggle room in case we decide not to use CSS in the future. See below.
Ah, so implementation in the sense of 'in this release of the TEI Guidelines'? Yes, below.
You are right that at the bottom of the Output Rendition section we could say something about 'Why CSS', but this is for the same reason that we suggest elsewhere inside the <rendition> element as a formally declared stylesheet language. This might suggest that we should be having a @scheme attribute like <rendition> with css as a value? Well, that's one of my major unresolved questions. *Do* we want to permit anything other than CSS?
I think we should probably mirror what we do on <rendition> where it is possible to use something else, but all our examples and recommendation is to use CSS where possible.
Much clearer, thanks.
thanks. -James -- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford