From: Hans Hagen <pragma@wxs.nl>
To: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: xml and lua again
Date: Mon, 24 Oct 2011 14:26:50 +0200 [thread overview]
Message-ID: <4EA5598A.4060109@wxs.nl> (raw)
In-Reply-To: <4EA55792.9090408@uni-bonn.de>
On 24-10-2011 14:18, Thomas A. Schmitz wrote:
> On 10/24/2011 12:17 PM, Hans Hagen wrote:
>> why so complex
>
> Hi Hans,
>
> yes, I'm aware that this procedure is quite silly for this example, this
> was just for myself, for educational purposes. As soon as the setup
> becomes more complex, I thought it might be easier to collect and
> process the options in lua than in tex (as I have done before), but I'm
> running against a wall here (see my exchange with Peter about goat milk
> yesterday). So the real question is: how can I collect data such as an
> attribute value to process it with lua, say in the form
>
> if lxml.att(t, "frame") == "on" then
> context("Yes, the frame is really on!")
> else
> context("Nope, sorry, it's still off.")
> end
>
> I don't really understand what kind of object a call such as lxml.att(t,
> "frame") produces.
all lxml.* calls print something to tex, so when you're at the lua end
and want to stay there you should use the xml.* methods; also, when you
have an element, say e then there is an e.at table that has all
attributes
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2011-10-24 12:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-22 16:46 Thomas A. Schmitz
2011-10-23 14:04 ` Peter Rolf
2011-10-23 14:37 ` Thomas A. Schmitz
2011-10-23 15:25 ` Peter Rolf
2011-10-23 18:15 ` Peter Rolf
2011-10-24 10:17 ` Hans Hagen
2011-10-24 12:18 ` Thomas A. Schmitz
2011-10-24 12:26 ` Hans Hagen [this message]
2011-10-24 17:00 ` Thomas A. Schmitz
2011-10-24 18:48 ` Hans Hagen
2011-10-25 9:43 ` Thomas A. Schmitz
2011-10-25 10:10 ` Wolfgang Schuster
2011-10-25 10:17 ` Hans Hagen
2011-10-25 10:27 ` Thomas A. Schmitz
2011-10-27 9:23 ` Thomas A. Schmitz
2011-10-27 9:53 ` Wolfgang Schuster
2011-10-27 10:32 ` Thomas A. Schmitz
2011-10-27 11:05 ` Hans Hagen
2011-10-28 6:23 ` Thomas A. Schmitz
2011-10-28 6:37 ` luigi scarso
2011-10-28 6:43 ` luigi scarso
2011-10-28 6:44 ` Patrick Gundlach
2011-10-28 6:55 ` Thomas A. Schmitz
2011-10-28 8:35 ` Wolfgang Schuster
2011-10-28 8:59 ` Hans Hagen
2011-10-28 8:56 ` Hans Hagen
2011-10-28 10:48 ` Thomas A. Schmitz
2011-10-28 11:23 ` luigi scarso
2011-10-28 11:42 ` Hans Hagen
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=4EA5598A.4060109@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=thomas.schmitz@uni-bonn.de \
/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).