From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: reStructuredText module
Date: Tue, 12 Mar 2013 16:57:49 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.02.1303121651550.15671@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <20130312202355.GA8066@phlegethon>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1918 bytes --]
On Tue, 12 Mar 2013, Philipp Gesang wrote:
> Nevertheless, I added some code to handle container directives:
> at the moment they simply map to macros of the same name.
> Existence of the macro is tested for at runtime, so you can place
> the definitions in your preamble. Example:
>
> ·································································
>
> This is a paragraph.
>
> .. container:: xyzzy
>
> whatever
>
> foo **bar** baz
>
> This is another paragraph.
>
> ·································································
>
> This will generate the output:
>
> ·································································
>
> \startparagraph
> This is a paragraph.
> \stopparagraph
>
> \ifcsname xyzzy\endcsname%
> \csname xyzzy\endcsname%
> {whatever foo {\sc bar} baz}%
> \else
> {whatever foo {\sc bar} baz}%
> \fi
>
>
> \startparagraph
> This is another paragraph.
> \stopparagraph
>
> ·································································
A better way to handle this is to provide macros \startRSTcontainer ...
\stopRSTcontainer and translate the above to
\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), providing such a container might be as simple as
\let\startRSTcontainer=\startframedtext
\let\stopRSTcontainer=\stopframedtext
or
\let\startRSTcontainer=\startparagraph
\let\stopRSTcontainer=\stopparagraph
Aditya
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2013-03-12 20:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 23:28 Bill Meahan
2013-03-12 0:31 ` Philipp Gesang
2013-03-12 12:28 ` Bill Meahan
2013-03-12 20:23 ` Philipp Gesang
2013-03-12 20:57 ` Aditya Mahajan [this message]
2013-03-12 21:42 ` Philipp Gesang
2013-03-12 23:21 ` Aditya Mahajan
2013-03-14 7:32 ` Keith J. Schultz
2013-03-14 16:02 ` Bug in \start (Re: reStructuredText module) Aditya Mahajan
2013-03-14 16:54 ` Hans Hagen
2013-03-14 17:17 ` reStructuredText module Philipp Gesang
2013-03-14 17:40 ` Marco Patzer
2013-03-14 17:57 ` Hans Hagen
2013-03-14 20:02 ` Aditya Mahajan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.02.1303121651550.15671@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).