ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: How to debug XML processing
Date: Sun, 20 Oct 2013 07:05:36 +0900	[thread overview]
Message-ID: <52630230.8000004@wxs.nl> (raw)
In-Reply-To: <52627E15.8030400@uni-bonn.de>

On 10/19/2013 9:41 PM, 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.

in most cases the filtering is is straightforward: \xmlflush, xmlfirst, 
xmlall + a simple path into the tree (relative to the current node)

it becomes more complex if data has to come from other places (combining 
xml nodes) but once you need that, you probably know what you're dealing 
with anyway

concerning tracing: there are some trackers  (lxml.*) that show the 
results of filtering, and if you want to see what goes in deep down you 
can try

\enabletrackers[context*]

but this also shows data generated and passes by other mechamisms.

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
___________________________________________________________________________________


      parent reply	other threads:[~2013-10-19 22:05 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
2013-10-19 22:05     ` Hans Hagen [this message]

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=52630230.8000004@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).