From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TEI to context XML mappings?
Date: Wed, 24 Feb 2016 15:32:25 +0100 [thread overview]
Message-ID: <56CDBEF9.4060507@uni-bonn.de> (raw)
In-Reply-To: <56CDBB1C.6050300@wxs.nl>
On 02/24/2016 03:15 PM, Hans Hagen wrote:
>
> if you need more info i can add it ... one can then generate whatever
> table one wants
>
> elements in element .. one level i assume?
Yes, one level, otherwise things become too complex. And you're right,
it's already there in the "children" element. My question was not so
much about the information but about the visualization. Let's put it in
a slightly different way: the context parser holds the information about
my xml tree as a lua table, right? It would be handy to have a typeset
version of this table, as a, well, table, so we could see how to access
the different parts of it in lua and/or tex code. So I know that my
element is e, I know that it has a table e.at that collects the
different attributes in subtables of the form e.at["attribute"]. I
assume there's also e.text, e.first etc. Would it be possible to typeset
this information for elements.
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:[~2016-02-24 14:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 21:26 Mica Semrick
2016-02-24 8:20 ` Hans Hagen
2016-02-24 9:10 ` Pablo Rodriguez
2016-02-24 9:52 ` Hans Hagen
2016-02-24 10:11 ` Thomas A. Schmitz
2016-02-24 10:26 ` Hans Hagen
2016-02-24 12:05 ` Thomas A. Schmitz
2016-02-24 14:15 ` Hans Hagen
2016-02-24 14:32 ` Thomas A. Schmitz [this message]
2016-02-24 14:51 ` Hans Hagen
2016-02-24 15:57 ` Thomas A. Schmitz
2016-02-24 17:32 ` Mica Semrick
2016-02-24 15:34 ` Mica Semrick
2016-02-24 10:32 ` Pablo Rodriguez
2016-02-25 5:04 ` mica
2016-02-25 9:48 ` Hans Hagen
2016-02-26 7:52 ` Pablo Rodriguez
2016-02-26 9:00 ` Hans Hagen
2016-02-26 15:39 ` Mica Semrick
2016-06-22 5:12 ` Mica Semrick
2016-08-14 5:03 ` Mica Semrick
2016-08-14 13:38 ` 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=56CDBEF9.4060507@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).