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: Mon, 17 Dec 2001 09:55:49 +0100	[thread overview]
Message-ID: <5.1.0.14.1.20011217095234.03241958@server-1> (raw)
In-Reply-To: <Pine.LNX.4.21.0112151800090.6750-100000@x.opf.slu.cz>

At 06:03 PM 12/15/2001 +0100, Lukas Kubin wrote:
>Maybe this question is better to Hans Hagen directly:
>Is it possible (or do you plan it) to get a plain ConTeXt source file as
>a result of mapping the ConTeXt code to XML? I wish to get the code after
>changing XML elements into ConTeXt according to my mapping file and before
>it is translated by ConTeXt into dvi, pdf ...
>Thank you.

I'm not sure if I understand you right.

You want

\defineXMLenvironment[test]
   {\startnarrower[2*left]}
   {\stopnarrower}

\startXMLdata
<test>
bla bla
</test>
\stopXMLdata

to produce

\startnarrower[2*left]
bla bla
\stopnarrrower

as output?

Not a real problem (did a quick test here), but for what purpose? There is 
for instance some formatting involved.

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
-------------------------------------------------------------------------


  reply	other threads:[~2001-12-17  8:55 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 [this message]
     [not found]   ` <Pine.LNX.4.21.0112191812550.2947-100000@x.opf.slu.cz>
2001-12-21  9:14     ` Hans Hagen
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.20011217095234.03241958@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).