Open scottkleinman opened 10 years ago
Yes, I think am[@ rend] is right and least obtrusive.
I don't suppose we have a list of elements on which we want or would like to put @ rend...? It would help for adjusting the XSL. I'll make my best guess the next time I get XSL-editing time, and we can refine from there. At the moment, only p and hi are sniffed for it, IIRC.
ETA Since reply via email doesn't shake hands with Markdown, I've added a space after @ to prevent invocation of the user named rend. (FFS.)
It should be possible to do that. I'll look into it.
Here's a start.
Guidelines explicitly state that the element takes @rend
:
Guidelines state that appropriate block-level elements can take @rend
. This presumably includes:
Suggested from this thread:
Thanks!
In practice, I'd be surprised if we needed @rend
on divn.
Me too. I just grabbed the list of "higher-level block elements" from our Guidelines, but I didn't really think that @rend
is appropriate for all of them.
I need actually to add them in the css file.
I recently came across "with" abbreviated "wt". Is the most efficient way to encode this as follows?
I don't want to use a combining "t" character since the "t" is not directly above the preceding character, and embedding
<hi>
inside<am>
is not allowed in our current schema.