···<date: 2013-03-12, Tuesday>···<from: Aditya Mahajan>···

> On Tue, 12 Mar 2013, Philipp Gesang wrote:
> 
> A better way to handle this is to provide macros \startRSTcontainer
> ... \stopRSTcontainer and translate the above to

I considered adding a generator \defineRSTcontainer with the
usual interface (e.g. [command=\framed,frame=on]). This won’t
work because the output is supposed to be a self-contained
document. The goal is for the output to consist of ordinary
Context macros only so it can be imported without loading further
code. (I’m undecided regarding the requirement of the “\RST...”
prefix, though.)

> \startRSTcontainer[xyzzy][...settings ....]
> ....
> \stopRSTcontainer
> 
> It should be responsiblility of the document author to make sure
> that the containers work correctly.
> 
> Depending on what containers are supposed to do (I have not read the
> links posted in this thread),

They are defined as HTML div’s.

>                               providing such a container might be as
> simple as
> 
> \let\startRSTcontainer=\startframedtext
> \let\stopRSTcontainer=\stopframedtext
> 
> or
> 
> \let\startRSTcontainer=\startparagraph
> \let\stopRSTcontainer=\stopparagraph

Honestly, I have no idea. Depending on the style sheet a div can
be a float or aligned or have a shaded background. The current
approach leaves the implementation to the user.

Philipp

-- 
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments