[Docutils-develop] Re: [Docutils-users] Custom behaviour in reST

[Magnus <ma...@th...>]

At 17:49 2003-05-01 -0400, David Goodger wrote:
>[Magnus Lyck=E5]
>>If I understand you correctly, your thought is that all the drivers
>>should be extended to know how to render "keyword", "string", "expression"
>>etc. But that means that I need to patch the drivers if I make a new
>>format which will introduce some new concept.
>
>No; look again, closely.  There's no more "<keyword>", it's now '<phrase=20
>class=3D"keyword">'.

I know, that's not what I meant.

>The difference is that Writers need only support the one element=20
>("phrase") and may ignore the class attributes if they don't support=20
>them.  Worst case: the output isn't colorful or styled.  In the case of=20
>HTML, the "class" attributes get passed through to the output, so they can=
=20
>interact with the stylesheet.  Other formats have a similar capacity.

Really? I fully understand how you think with HTML/CSS. The
only requirement there is that the CSS file is "aware" of the
keyword and expression etc classes.

I didn't know there was any corresponding mechanism for e.g.
PDF though. LaTeX obviously have .sty or .cls files (even if
that's always seemed a bit magic to me).

I guess it depends on how "odd" things we would like to be able
to do with the directives. If it always boils down to a text
string with a simple label that CSS or something similar
understands, then I suppose this is ok.

I'll be back when I come up with something that won't fit in
this model (if ever)... ;)


--
Magnus Lycka (It's really Lyck&aring;), ma...@th...
Thinkware AB, Sweden, www.thinkware.se
I code Python ~ The shortest path from thought to working program=20