From: "Procházka Lukáš Ing. - Pontex s. r. o." <LPr@pontex.cz>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Ctx & XML
Date: Thu, 11 Dec 2014 12:25:05 +0100 [thread overview]
Message-ID: <op.xqpbb3qttpjj8f@lpr> (raw)
In-Reply-To: <54895F78.6080309@wxs.nl>
Hello Hans,
On Thu, 11 Dec 2014 10:10:16 +0100, Hans Hagen <pragma@wxs.nl> wrote:
>
> that already makes assumptions that it's just data ... the context xml
> parser is a roundtrip one so a bit more control is provided:
>
> local str = [[
> <?xml version="1.0" ?>
> <a one="1">
> <!-- rubish -->
> <b two="1"/>
> <b two="2">
> c > d
> </b>
> </a>
> ]]
>
> I've added some flags:
>
> inspect(xml.totable(xml.convert(str)))
>
> table={
> {
> "xml version=\"1.0\" ",
> ["_type"]="instruction",
> },
> "\
> ",
> {
> "\
> ",
> {
> " rubish ",
> ["_type"]="comment",
> },
> "\
> ",
> {
> ["_tag"]="b",
> ["_type"]="_element",
> ["two"]="1",
> },
> "\
> ",
> {
> "\
> c > d\
> ",
> ["_tag"]="b",
> ["_type"]="_element",
> ["two"]="2",
> },
> "\
> ",
> ["_tag"]="a",
> ["_type"]="_element",
> ["one"]="1",
> },
> ["_type"]="root",
> }
>
> inspect(xml.totable(xml.convert(str),true))
>
> table={
> {
> "xml version=\"1.0\"",
> ["_type"]="instruction",
> },
> {
> {
> "rubish",
> ["_type"]="comment",
> },
> {
> ["_tag"]="b",
> ["_type"]="_element",
> ["two"]="1",
> },
> {
> "c > d",
> ["_tag"]="b",
> ["_type"]="_element",
> ["two"]="2",
> },
> ["_tag"]="a",
> ["_type"]="_element",
> ["one"]="1",
> },
> ["_type"]="root",
> }
>
> inspect(xml.totable(xml.convert(str),true,true))
>
> table={
> {
> [0]="a",
> {
> [0]="b",
> ["two"]="1",
> },
> {
> [0]="b",
> "c > d",
> ["two"]="2",
> },
> ["one"]="1",
> },
> }
>
> The last one is yours. Of course in all cases you loose info that is
> present in the original representation (where you can also access the
> nodes via expressions). Don't expect additional helpers for this
> 'totable' variant.
this is great. I'll try it...
Thank you.
BTW: In your example, you are using the following enum of "_type":
"instruction",
"comment",
"_element", <-- REALLY UNDERSCORE here?
"root",
Best regards,
Lukas
>
> Hans
--
Ing. Lukáš Procházka | mailto:LPr@pontex.cz
Pontex s. r. o. | mailto:pontex@pontex.cz | http://www.pontex.cz
Bezová 1658
147 14 Praha 4
Tel: +420 241 096 751
Fax: +420 244 461 038
___________________________________________________________________________________
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 11:25 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
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. [this message]
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=op.xqpbb3qttpjj8f@lpr \
--to=lpr@pontex.cz \
--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).