From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Ctx & XML
Date: Thu, 11 Dec 2014 02:24:24 +0100 [thread overview]
Message-ID: <5488F248.5080408@wxs.nl> (raw)
In-Reply-To: <op.xqoafwn7f14xzu@lkzd-2013>
On 12/10/2014 11:08 PM, Lukáš Procházka wrote:
> Hello,
>
> I'm having problem using LuaXml library with Ctx, both using Lua ver. 5.2.
>
> LuaXml works fine with Lua standalone programs/scripts;
> but something weird occurs when used from within Ctx (e.g. a .xml file
> can be read successfully from standalone Lua with LuaXml lib; but the
> same code doesn't give the desired result when used in combination with
> Ctx; a problem might be version mismatch - I'm still using both Lua 5.1
> and 5.2 including 3rd party modules in my scripts - but my latest tests
> with Ctx & LuaXml should have avoid this; or namespace mismatch...?).
I don't know (and as we have quite some code on-board I don't care too
much either about clashes in namespaces).
> Anyway, does native Ctx XML API (has it its own namespace, like
> 'context.xml'?) provide a function to load a .xml file and to return its
> XML tree as a table, with nodes (as a table with node attributes as
> table members) in a proper sequence... something like LuaXml's
> 'xml.load("file.xml")' does?
I assume that you also want the content of elements, not just the
attributes.
> Or how to achieve this in a best way under Ctx: XML file -> Lua table/tree?
It all depends on what kin dof table you want (if the content is an
indexed table and attributes keys then you have the problem that the
element cannot be a key too as it can clash) .. anyway, it's no big deal
to provide a stupid table, so I can provide something because after all
the loaded xml file is a table already.
local x = xml.load("file.xml")
local t = xml.totable(x)
where x is an index/hash mix plus _tag, _type and _namespace fields as
well (after all I assume that you need to know that too).
(btw, I bet that you can do what you want with the existing
functionality as well, so there is not much benefit in such a table)
Probably in the next upload,
Hans
-----------------------------------------------------------------
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:[~2014-12-11 1:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 22:08 Lukáš Procházka
2014-12-11 1:24 ` Hans Hagen [this message]
2014-12-11 7:33 ` Procházka Lukáš Ing. - Pontex s. r. o.
2014-12-11 9:10 ` Hans Hagen
2014-12-11 11:25 ` Procházka Lukáš Ing. - Pontex s. r. o.
2014-12-11 13:09 ` 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=5488F248.5080408@wxs.nl \
--to=pragma@wxs.nl \
--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).