ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: stephleg@free.fr
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: How to debug XML processing
Date: Fri, 18 Oct 2013 15:22:40 +0200 (CEST)	[thread overview]
Message-ID: <33536258.250373553.1382102560348.JavaMail.root@zimbra71-e12.priv.proxad.net> (raw)
In-Reply-To: <882979226.250349853.1382101907031.JavaMail.root@zimbra71-e12.priv.proxad.net>

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.

Regards,
Stéphane.
___________________________________________________________________________________
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
___________________________________________________________________________________

       reply	other threads:[~2013-10-18 13:22 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 [this message]
2013-10-19 12:41   ` Thomas A. Schmitz
2013-10-19 17:29     ` Aditya Mahajan
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=33536258.250373553.1382102560348.JavaMail.root@zimbra71-e12.priv.proxad.net \
    --to=stephleg@free.fr \
    --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).