From: "Kevin D. Robbins" <robbins.kevin.d@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Is it possible to pass unmarked paragraphs into Lua for processing
Date: Fri, 15 Oct 2010 15:36:50 -0600 [thread overview]
Message-ID: <AANLkTin=64hFYuv3vr9n+BKF39gF83yC0j+dLp2rKijF@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1010141742220.32532@ybpnyubfg.ybpnyqbznva>
[-- Attachment #1.1: Type: text/plain, Size: 2287 bytes --]
I confess, I hadn't considered anything quite so bold as reading the whole
of the text into Lua and then processing it back out. I suppose I was
expecting one of the true TeXperts to offer suggestions involving
\appendtoks ... \to \everypar.
I also realized that I forgot to mention that I want to be able to do this
all while using the ConTeXt project/product/component support.
Any other suggestions on how I could process unmarked paragraphs in Lua?
Kevin
On Thu, Oct 14, 2010 at 3:48 PM, Aditya Mahajan <adityam@umich.edu> wrote:
> On Thu, 14 Oct 2010, Kevin D. Robbins wrote:
>
> Hi all,
>>
>> I am wondering if and how it might be possible to catch all unmarked
>> paragraphs in a TeX file and pass them into Lua. So, in the following
>> example, each of the first three unmarked paragraphs would be passed to
>> the
>> Lua function "process_paragraph" for optional processing, but the fourth
>> paragraph between \startmarkedparagraph...\stopmarkedparagraph would not
>> be
>> passed to "process_paragraph".
>>
>
> If you are willing to add some more markup, then you can do
>
> \starttext
> \startMarking
> ...
> \startmarkedparagraph
> ...
> \stopmarkedparagraph
> \stopMarking
> \stoptext
>
> where \startMarking .. \stopMarking passes everything to lua (
> http://wiki.contextgarden.net/Programming_in_LuaTeX#Manipulating_verbatim_text_for_dummies)
> and you can then search for \startmarkedparagraph ... \stopmarkedparagraph
> in lua.
>
> Or you could just redefine \starttext ... \stoptext to do the capturing.
> Something like:
>
> \let\normalstarttext\starttext
> \let\normalstoptext\stoptext
>
> \def\starttext{....}
>
> And in the lua end call \normalstarttext before starting typesetting and
> \normalstoptext after all typesetting is done.
>
> Aditya
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 3356 bytes --]
[-- Attachment #2: Type: text/plain, Size: 486 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
___________________________________________________________________________________
prev parent reply other threads:[~2010-10-15 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-14 21:21 Kevin D. Robbins
2010-10-14 21:48 ` Aditya Mahajan
2010-10-15 21:36 ` Kevin D. Robbins [this message]
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='AANLkTin=64hFYuv3vr9n+BKF39gF83yC0j+dLp2rKijF@mail.gmail.com' \
--to=robbins.kevin.d@gmail.com \
--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).