ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: reStructuredText module
Date: Tue, 12 Mar 2013 19:21:05 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.02.1303121904480.28048@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <20130312214225.GA11494@phlegethon>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2208 bytes --]

On Tue, 12 Mar 2013, Philipp Gesang wrote:

> ···<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.)

Personally, I think that it is reasonable to expect the users to import a 
module.

> 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.

Another option is to change the generated output to

     \start[xyzzy]
     ....
     \stop

When the environment xyzzy exists, this is (supposed to be, see below) 
equivalent to

     \startxyzzy
     ....
     \stopxyzzy

otherwise, this is equivalent to

     \bgroup
     ....
     \egroup

This way, you maintain your goal of having output that runs out of the 
box, but at the same time generate readable code. It can then be left upto 
the user to define the xyzzy environment (Of course, this method does not 
support passing arguments to environment, but then neither does your 
proposed solution).

@Hans, there is a bug in core-sys.mkiv: There is a missing \expandafter, and
currentstartstop should be changed to m_syst_start_stop.

\def\syst_start_yes[#1]%
   {\edef\m_syst_start_stop{#1}%
    \ifx\m_syst_start_stop\empty
      \let\syst_stop_indeed\donothing
    \else\ifcsname\e!start\m_syst_start_stop\endcsname
      \expandafter\let\expandafter\syst_stop_indeed\csname\e!stop\m_syst_start_stop\endcsname
      \csname\e!start\m_syst_start_stop\expandafter\expandafter\expandafter\endcsname
    \else
      \let\syst_stop_indeed\donothing
    \fi\fi}

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
___________________________________________________________________________________

  reply	other threads:[~2013-03-12 23:21 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
2013-03-12 21:42         ` Philipp Gesang
2013-03-12 23:21           ` Aditya Mahajan [this message]
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.1303121904480.28048@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).