From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to debug XML processing
Date: Sat, 19 Oct 2013 13:29:22 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1310191324140.2028@nqv-guvaxcnq> (raw)
In-Reply-To: <52627E15.8030400@uni-bonn.de>
On Sat, 19 Oct 2013, Thomas A. Schmitz wrote:
> On 10/18/2013 03:22 PM, stephleg@free.fr wrote:
>> Hello,
>>
>> After reading "Getting Web Content and pdf-Output from One Source" by
>> Thomas A. Schmitz, i'm trying to use the same method to build a PDF
>> file from a HTML one. But i quickly found that when something doesn't
>> work as expected, it's pretty hard to debug because it's hard to tell
>> if the error come from the environment file, the lua code or
>> something else.
>>
>> So are there some useful tricks to debug this kind of processing
>> besides the \enabletrackers command? Especially is there a way to
>> view the generated ConTeXt code after the macro expansion?
>>
>> Thank you.
>
> Let me put it this way: if there is a way, I don't know about it. You're
> right that debugging becomes more complex because there are more layers of
> complexity involved. OTOH: many editors can validate xml as you type (I don't
> know of any that does the same for TeX input), so at least you know when your
> source should compile. And one tip (something I have started too late): put
> your lua code in a separate file and call it from within your TeX
> environment, that way, context's error messages become more precise.
I find it difficult to wrap my head around the XML processing details,
mainly because I don't understand how XPATH works (there are subtle
difference between XPATH tutorials that I find online and ConTeXt
implementation of it). I find it easier to:
1. Keep the data as an XML source file and create a RNG schema to validate
it.
2. Trasform XML into LUA tables. I use the lxml library (that comes with
ConTeXt) to do this translation.
3. Format the LUA data using CDL (ConTeXt Lua Document).
This way, the parsing is separate from formatting and it is easy to verify
both parts independently.
Aditya
___________________________________________________________________________________
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-10-19 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <882979226.250349853.1382101907031.JavaMail.root@zimbra71-e12.priv.proxad.net>
2013-10-18 13:22 ` stephleg
2013-10-19 12:41 ` Thomas A. Schmitz
2013-10-19 17:29 ` Aditya Mahajan [this message]
2013-10-19 22:05 ` 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=alpine.DEB.2.02.1310191324140.2028@nqv-guvaxcnq \
--to=adityam@umich.edu \
--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).