Our local practice here since the introduction of P5 is to use
@rendition in roughly the way HTML @class is used (as a
pointer to a style description stored elsewhere), and to use @rend as a
precise equivalent of HTML @style, i.e., it is expected to contain a
string that parses into one or more CSS rules.
So, for example, we mark a hanging paragraph
where the <tagsDecl> in our header contains
<rendition xml:id="hanging" scheme="css">text-indent: -1em;
but for a paragraph with an ad hoc style we would use something like
<p rend="font-family: 'Comic Sans MS', fantasy; color: red;
border: 1px solid blue;">
We're encoding modern printed texts, where CSS is usually adequate to
capture the rendering of the original.
On Wed, 14 Jan 2009, Lou Burnard wrote:
> Hi Martin
> In P5 we introduced a new slightly more explicitly structured version of
> @rend, confusingly called @rendition, together with an element <rendition>
> You might find these useful: there are some examples of how to embed CSS
> descriptions in your document using them at
> There are definitely things that CSS cannot do (like ignore or re-arrange
> parts of the input for example) but that certainly doesn't mean it's not
> Martin Holmes wrote:
> > Hi all,
> > The global attribute @rend is wonderfully loose ("any string of characters",
> > "These Guidelines make no binding recommendations for the values of the
> > @rend attribute..."). However, I'm increasingly finding that CSS is
> > everything I need and more for the @rend attribute, and in a current
> > project, I'm considering converting all my old formulations (rend="italic"
> > etc., derived from old usage, examples and guidelines) over to pure CSS
> > (rend="font-style: italic").
> > Can anyone see any objection to this on principle? Have you come across any
> > rendering features which are impossible to describe in CSS?
> > Cheers,
> > Martin
David Sewell, Editorial and Technical Manager
ROTUNDA, The University of Virginia Press
PO Box 801079, Charlottesville, VA 22904-4318 USA
Courier: 310 Old Ivy Way, Suite 302, Charlottesville VA 22903
Email: [log in to unmask] Tel: +1 434 924 9973