Hi Martin,

I mentioned this topic in my recent posting in the rend thread. (Any 
responses to that posting from anyone would still be appreciated)

I think there really needs to be added some kind of @scope attribute to 
<rendition/> to be able to handle such CSS pseudo-elements in a 
cross-project reliable manner. In this case, it might look like this:

<rendition xml:id="parMarker" scheme="css" scope="before">content: 
<p rendition="#parMarker">Four score and seven years ago...</p>

While James' suggestion to just use XSLT would work fine, it doesn't 
encode the original formatting of the document in a standard fashion 
that could be replicated by other consumers of the document (who might 
use automated tools or be unaware of the particular conventions of the 
project's stylesheet). The more projects rely on such conventions (if 
they can be formalized), the more easy I think it would be for tools 
(such as general-purpose stylesheets, browsers, etc.) to work with them 
into the future.

I added this as a feature request at


On 1/21/2009 7:07 AM, Martin Holmes wrote:
> This looks like a job for the CSS pseudo-element :before:
> X:before{
>     content: "¶";
> }
> although I'm not sure how you'd hook this into @rend or @rendition.
> Cheers,
> Martin
> Robert Whalen wrote:
>> Head titles in a book of poems are each preceded by a pilcrow (U 
>> +00B6). I am inclined to use <fw/> but hesitate as to whether this  
>> qualifies as "similar material," i.e., "a running head (e.g. a  
>> header, footer), catchword, or similar material." Clearly this is 
>> not  header or footer material, but it is a repeated formal feature 
>> of no  semantic significance to the text it precedes, i.e., the poem 
>> title  within <head/>. How are others dealing with this (if you've  
>> encountered it)?
>> Rob