[tei-council] rendition, rend, and style
Arianna Ciula
arianna.ciula at kcl.ac.uk
Thu May 10 13:01:43 EDT 2007
I totally agree with what David says about the meaning of @rend for not
born digital material.
As far as born digital material regard though, I can imagine the
situation where someone wants to differentiate the semantics (not big or
small, but myIntrepret_category1 and myIntrepret_category2) of the
information so that some style could be applied - possibly - later on.
We should remember that in some cases the people who do the markup are
not bothered (should they be?) about what style is going to be applied
to their documents, but they do want to differentiate between different
things that may need a different visualisation. So while I can see the
advantages of a good practice in pointing @rend to <rendition> in the
header for born digital material, I am still not sure this is the only
use we should support for @rend in this case.
Arianna
Lou's Laptop wrote:
> Sebastian Rahtz wrote:
>> If @rend says it is for source description only,
>> then my born-digital document
>> can't use it.
> Hmm, I may be logic chopping here, but I don't think I agree. If your
> doc is born digital, then you *are* describing the source when you say
> @rend=sup, surely?
>
> Maybe this is one of the points that needs more careful elaboration. Can
> we imagine a case where @rend in a born-digital document does not
> describe how it should be rendered? @rend="done in emacs without benefit
> of markup" doesnt seem very likely.
>
> _______________________________________________
> tei-council mailing list
> tei-council at lists.village.Virginia.EDU
> http://lists.village.Virginia.EDU/mailman/listinfo/tei-council
--
Dr Arianna Ciula
Research Associate
Centre for Computing in the Humanities
King's College London
Strand
London WC2R 2LS (UK)
Tel: +44 (0)20 78481945
http://www.kcl.ac.uk/cch
More information about the tei-council
mailing list