[tei-council] Guidelines build temporarily borked

[Sebastian Rahtz]

On 30 Jul 2014, at 16:14, Martin Holmes <mholmes at uvic.ca> wrote:
> 
> The objective was to give a standardized replacement strategy for people moving from @type (where we did declare suggested values) and @rend.

Yes, and the problem there was that the old @type was _locally_ declared, in a way which
we want to get rid of, rather than being a member of att. typed, precisely because it had a valList.
We are reaping our own whirlwind here.

> I think if there is any value in having the Stylesheets render lists in predictable ways, then there have to be predictable values for @rend.

sure. you’re in TEI Simple territory now! but doing it just for <list>, in the base TEI, seems like asking for trouble. 

> We don't have to declare them in a valList, but if we don't override @rend, we have nowhere to suggest them other than in remarks, which is not ideal.
> 
you can do it in the prose….

>> sorting out the underlying processing code to support what you’ve (which was entirely
>> technically correct) will be hard; I at least wouldn’t look at it in time for next release,
>> and I suspect it would be a big ask for someone else to grok odd2dtd in a hurry
> 
> It depends on the release date, really, and we don't know that yet. The only real requirement is that the rendering for the Guidelines (HTML5, PDF and ePub) be working; all the other outputs can wait a while.

i assume the basic rendering is OK now? that use of @type has been supported for quite a whole now. 

the question is whether odd2dtd can supported your semi-open valList change in the source. nothing to do with rendering.
--
Sebastian Rahtz      
Director (Research) of Academic IT
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

Não sou nada.
Nunca serei nada.
Não posso querer ser nada.
À parte isso, tenho em mim todos os sonhos do mundo.