From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: {{ double braces }}
Date: Sat, 26 Jan 2008 11:52:37 +0100 [thread overview]
Message-ID: <479B10F5.6090309@elvenkind.com> (raw)
In-Reply-To: <111CFD7B-669B-4044-901A-0291DD898978@uni-bonn.de>
Thomas A. Schmitz wrote:
>
> You could also use a nice scripting language like ... lua!! lua has
> support for "balanced strings," so no nesting trickery is needed,
> see http://www.lua.org/pil/20.2.html
> (scroll to the bottom of the page). Or you could try and nag Hans
> into giving a nice tutorial on the lua lpeg library at Bohinj! :-)
Even in bare lua, it is very easy to match balanced braces:
local data = "\\footnote{x{y}z}"
local match = "\\footnote%s%b{}"
local i = 0
while true do
i,j = string.find(data, match, i+1)
if i == nil then break end
print(string.sub(data, i, j))
end
with lpeg, the code looks a bit harder, but is still short and
relatively shortforward:
local matchtable = { "TEXT",
SP = lpeg.S" \n\t"^0,
BODY = lpeg.P{ "{" * ((1 - lpeg.S"{}") + lpeg.V(1))^0 * "}" },
FOOTNOTE = lpeg.P"\\footnote" * lpeg.V"SP" * lpeg.V"BODY" / print,
TEXT = (lpeg.V"FOOTNOTE" + 1)^0 * -1,
}
lpeg.match(matchtable, data)
Best wishes,
Taco
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-01-26 10:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 14:45 Steffen Wolfrum
2008-01-21 15:02 ` Mikael Persson
2008-01-21 15:53 ` Steffen Wolfrum
2008-01-23 20:49 ` Peter Münster
2008-01-23 21:50 ` Peter Münster
2008-01-23 22:17 ` Thomas A. Schmitz
2008-01-23 23:19 ` Aditya Mahajan
2008-01-26 10:11 ` Thomas A. Schmitz
2008-02-06 7:01 ` Aditya Mahajan
2008-02-06 9:11 ` Steffen Wolfrum
2008-02-06 16:36 ` Aditya Mahajan
2008-02-06 19:20 ` Hans van der Meer
2008-02-06 20:01 ` Steffen Wolfrum
2008-02-06 20:16 ` Hans van der Meer
2008-02-06 20:17 ` Otared Kavian
2008-02-12 15:09 ` Thomas A. Schmitz
2008-02-12 15:15 ` Hans Hagen
2008-02-12 17:39 ` Aditya Mahajan
2008-02-13 8:39 ` Taco Hoekwater
2008-02-13 9:31 ` luigi scarso
2008-02-13 10:21 ` Taco Hoekwater
2008-02-13 10:38 ` luigi scarso
2008-01-26 10:52 ` Taco Hoekwater [this message]
2008-01-26 11:41 ` Taco Hoekwater
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=479B10F5.6090309@elvenkind.com \
--to=taco@elvenkind.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).