From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: XML Lua engine in ConTeXt
Date: Tue, 05 Mar 2013 11:38:03 +0100 [thread overview]
Message-ID: <5135CB0B.3040507@uni-bonn.de> (raw)
In-Reply-To: <op.wtgwpeygtpjj8f@lpr>
On 03/05/2013 10:59 AM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
> which XML processing Lua engine is used by ConTeXt?
>
> There are more XML processors developed for Lua - LuaXML, LuaExpat etc.
>
> Does ConTeXt use one of these or another, or its own - a built-in one?
>
> As I'm processing XML tables with pure Lua, too, I'd like to use only
> one engine in pure Lua scripts and within ConTeXt;
> I believe it could be possible.
Hans can give the authoritative answer, of course, but if you look into
http://www.pragma-ade.com/general/manuals/mk.pdf , chapter XVII, you
will see that he has indeed written his own parser, based on lpeg, and
not used any of the lua libraries (I'm not a programmer, so take my word
with a ton of salt, but I had a look at them and found them truly awful,
compared to what, e.g., python and perl have to offer).
Thomas
___________________________________________________________________________________
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-05 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 9:59 Procházka Lukáš Ing. - Pontex s. r. o.
2013-03-05 10:38 ` Thomas A. Schmitz [this message]
2013-03-05 10:54 ` 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=5135CB0B.3040507@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).