ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: ConTeXt file as a result of mapping
Date: Fri, 21 Dec 2001 10:14:03 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20011221101146.03d9d3a0@server-1> (raw)
In-Reply-To: <Pine.LNX.4.21.0112191812550.2947-100000@x.opf.slu.cz>

At 07:35 PM 12/20/2001 +0100, Lukas Kubin wrote:
>Now, when I wish to process XML document with ConTeXt, I have to write
>which XML elements to replace with which ConTeXt's. ConTeXt internaly
>exchanges it and translates into PDF, DVI, ... So no TeX document is on
>the way. I only have XML source, ConTeXt mapping and the result of TeX
>process (or is? maybe I just don't know how to get it). It might be useful
>to have the TeX file available for some specific changes. I could do it
>with XSLT but why, when I already did similar work with creating the
>XML->ConTeXt mapping file.
>I don't know  how hard this is to implement but maybe someone else would
>find it useful too.

You can probably do most of what you want by setting up context commands or 
create specific (new) instances of core functionality. Depends on what you 
want to change.

Another option is to add processing instructions (i.e. insert additional 
context code in the xml document)

Hans

-------------------------------------------------------------------------
                                   Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                       Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
  tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------


  parent reply	other threads:[~2001-12-21  9:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-15 17:03 Lukas Kubin
2001-12-17  8:55 ` Hans Hagen
     [not found]   ` <Pine.LNX.4.21.0112191812550.2947-100000@x.opf.slu.cz>
2001-12-21  9:14     ` Hans Hagen [this message]
2001-12-17 13:12 Patrick Gundlach

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=5.1.0.14.1.20011221101146.03d9d3a0@server-1 \
    --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).