[tei-council] P5 use of rend in examples

Fri Nov 11 16:29:03 EST 2011

+1 from me too. I'm happy to make suggestions about how to handle some 
of these in CSS. But I think we need to think about the CSS issue. If 
we're going to suggest that people use CSS -- as to be honest I think we 
should -- there is no better standard for describing the appearance, 
layout, etc. of rendered components of a document -- then we should 
agree that we will recommend it, and also agree on the overall strategy 
we are going to recommend.

For instance, we might choose to show all @rend attribute values as 
valid CSS, or we might choose the sort of bifurcated strategy I usually 
use, whereby any @rend value which contains a colon is parsed as CSS, 
and any that's not is treated as a class indicator (meaning that it 
constitutes the same kind of shorthand as an XHTML class attribute 
value, pointing to one or more CSS rulesets defined elsewhere.

There are also some slightly tricky issues to deal with, such as the 
fact that block-level CSS values have no effect on inline-level elements 
in e.g. XHTML; this is slightly tricky with TEI code because we have no 
definitive rules on when an element is inline and when it's block.

Cheers,
Martin

On 11-11-11 11:31 AM, Laurent Romary wrote:
> agree with the general strategy + align with CSS when applicable.
>
> Le 11 nov. 2011 à 11:27, Sebastian Rahtz a écrit :
>
>> I have put up a crude table at http://tei.oucs.ox.ac.uk/rends.html
>> which lists all the distinct pairs of rend value and element name
>> in the Guidelines.
>>
>> there are some weirdo things here
>>
>>   * the first 2 lines
>>   * "case(mixed)"
>>   * "small caps" (note space)
>>   * "small type flush left"
>>   * "scream"
>>
>> I'd make 4 observations:
>>
>>   - we should normnalize the it vs italics
>>   - we should rewrite things to not use spaces in phrases
>>   - I think the 'align(center) case(allcaps)' notation, which I think is Syd B's, is cute but misleading
>>      in this day and age, as it has not gain any traction or widespread implementation
>>   - we should avoid joky ones like "scream" which are rather specific to a culture and time….
>>
>> (the latter comes from
>> <head rend="scream" type="main">
>> Major agrees to enforced no-fly zone</head>)
>>
>> Lou, you may now disagree :-}
>> --
>> Stormageddon Rahtz
>> Head of Information and Support Group
>> Oxford University Computing Services
>> 13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431
>>
>> Sólo le pido a Dios
>> que el futuro no me sea indiferente
>>
>> _______________________________________________
>> tei-council mailing list
>> tei-council at lists.village.Virginia.EDU
>> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>>
>> PLEASE NOTE: postings to this list are publicly archived
>
> Laurent Romary
> INRIA&  HUB-IDSL
> laurent.romary at inria.fr
>
>
>
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
>
> PLEASE NOTE: postings to this list are publicly archived