From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: handling code in XML
Date: Sun, 22 Feb 2015 18:37:09 +0100 [thread overview]
Message-ID: <54EA13C5.4000200@gmx.es> (raw)
Dear list,
I have the following sample:
\startbuffer[demo]
<doc>
<p><code><div>foo</div></code></p>
<pre><code>for a > b
& c</code></pre>
</doc>
\stopbuffer
\starttext
\startxmlsetups xml:initialize
\xmlsetsetup{#1}{p|doc|code}{xml:*}
\xmlsetsetup{#1}{pre/code}{xml:pre}
\stopxmlsetups
\xmlregistersetup{xml:initialize}
\startxmlsetups xml:doc
\xmlflush{#1}
\stopxmlsetups
\startxmlsetups xml:p
\xmlflush{#1}\par
\stopxmlsetups
\startxmlsetups xml:code
\begingroup\tt\xmlflush{#1}\endgroup\par
\xmlinlineverbatim{#1}
\stopxmlsetups
\startxmlsetups xml:pre
\xmlverbatim{#1}
\stopxmlsetups
\xmlprocessbuffer{main}{demo}{}
\stoptext
And I experience two issues:
Is there a way to handle <code> (or <pre>) as verbatim, but translating
the five entities that need to be escaped in XML?
Which is the right way to link a <pre> or <code> to a type or typing
command?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
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 reply other threads:[~2015-02-22 17:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-22 17:37 Pablo Rodriguez [this message]
2015-02-23 14:56 ` Hans Hagen
2015-02-23 18:25 ` Pablo Rodriguez
2015-02-23 18:34 ` Hans Hagen
2015-02-23 19:29 ` Pablo Rodriguez
2015-02-24 14:07 ` Hans Hagen
2015-02-24 14:17 ` Hans Hagen
2015-02-24 14:41 ` Hans Hagen
2015-02-24 16:31 ` Pablo Rodriguez
2017-07-23 19:28 Pablo Rodriguez
2017-07-24 8:48 ` Hans Hagen
2017-07-24 19:34 ` Pablo Rodriguez
2017-07-24 8:54 ` 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=54EA13C5.4000200@gmx.es \
--to=oinos@gmx.es \
--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).