On Thu, Sep 9, 2010 at 6:57 PM, Martin Holmes <[log in to unmask]> wrote:
@rend may be used exactly as you want @tei:css to be used. You can be
explicit about your use of @rend in your headers. I think it's a
mistake to think that the proposed @tei:css could ever replace @rend.
How could even the ever-growing and evolving CSS ever anticipate or
accommodate the range of detail and description that one may want to
record about the style , the rendition, and the material object that
carries and is the text?
> What I'm suggesting is that @tei:css would be better than the current
> @rend, because it uses a formal language for which validators and
> parsers exist; that it could ultimately replace @rend, but could happily
> coexist alongside it for as long as necessary; and that it's a natural
> partner for the @rendition system, allowing inline styles alongside
> centralized classes (just as we have in HTML).
I sent the following to Martin earlier in this thread and
unintentionally neglected to send it to the list:
Putting CSS in @rend is perfectly acceptable. People put lots of
non-standard things in @rend, and there's no prohibition against
standard CSS. With the addition of @rendition, which explicitly
supports CSS, as Lou mentioned, one can think of @rendition as
analogous to html's @class and @rend as analogous to html's @style. I
don't see any need for a new attribute. @rend allows CSS values;
@rendition encourages CSS values. And both allow for other values for
things that cannot be expressed using CSS. And of course we have the
encodingDesc in the header to be very clear about our usage of these
rendition-related elements and attributes. Surely the infrastructure
is already there to provide robust support for CSS, other style and
presentation standards, and home-grown style languages.
| John A. Walsh
| Assistant Professor, School of Library and Information Science
| Indiana University, 1320 East Tenth Street, Bloomington, IN 47405
| www: <http://www.slis.indiana.edu/faculty/jawalsh/>
| Voice:812-856-0707 Fax:812-856-2062 <mailto:[log in to unmask]>