From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Pablo Rodriguez <oinos@gmx.es>
Subject: Re: handling code in XML
Date: Mon, 24 Jul 2017 10:48:02 +0200 [thread overview]
Message-ID: <d878f631-1967-d332-1320-90e49a82de1c@wxs.nl> (raw)
In-Reply-To: <bee33963-6ef5-7b7b-9d60-674a29ce00ce@gmx.es>
On 7/23/2017 9:28 PM, Pablo Rodriguez wrote:
> Hans,
>
> I have the following sample:
>
> \startbuffer[demo]
> <doc>
> <div>
> <source>\command[option=value]{text "<&>"}</source>
> </div>
>
> <div class="sourceCode">
> <pre class="sourceCode tex">
> <code class="sourceCode latex">
> <span class="fu">\command</span>[option=value]{text
> "<&>"}
> </code>
> </pre>
> </div>
> </doc>
> \stopbuffer
>
> \startxmlsetups xml:initialize
> \xmlsetsetup{#1}{doc|source|div|span}{xml:*}
> \xmlsetsetup{\xmldocument}
> {pre[contains(@class,'sourceCode')]/
> code[contains(@class,'sourceCode')]}
> {xml:pre:code}
> \stopxmlsetups
>
> \xmlregistersetup{xml:initialize}
>
> \startxmlsetups xml:doc
> \xmlflush{#1}
> \stopxmlsetups
>
> \startxmlsetups xml:div
> \xmlflush{#1}
> \stopxmlsetups
>
> \startxmlsetups xml:source
> \xmlprettyprint{#1}{tex}
> \stopxmlsetups
>
> \startxmlsetups xml:pre:code
> \xmlflushspacewise{#1}
> \stopxmlsetups
>
> \startxmlsetups xml:span
> \bgroup\xmlflush{#1}\egroup
> \stopxmlsetups
>
> The .sourceCode elements are the standard way in which pandoc serves
> colored code. I have to deal with them.
>
> In the sample above, for xml:pre:code, I would need and expanded
> \xmlprettyprint that also ignores tags inside (anything between < and >,
> but not the entities).
>
> Which is the way to get this expanded \xmlprettyprint?
The xml that we see is getting more weird every day .. anyway
\startluacode
function lxml.tobufferX(id,pattern,name)
local collected = xml.applylpath(lxml.getid(id),pattern)
if collected then
local t = { }
xml.string(collected[1],function(s) t[#t+1] = s end)
buffers.assign(name,table.concat(t))
else
buffers.erase(name)
end
end
\stopluacode
\unprotect
\unexpanded\def\xmlprettyprinttext#1#2%
{\ctxlua{lxml.tobufferX("#1",".","xml-temp")}%
\ifdefined\scitebuffer
\scitebuffer[#2][xml-temp]%
\else
\typebuffer[xml-temp][\c!option=#2]%
\fi}
\protect
I'll add \xmlprettyprinttext to the core (somewhat different
implementation) so that you can do
\startxmlsetups xml:source
\xmlprettyprinttext{#1}{tex}
\stopxmlsetups
\startxmlsetups xml:pre:code
\xmlprettyprinttext{#1}{tex}
\stopxmlsetups
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-07-24 8:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 19:28 Pablo Rodriguez
2017-07-24 8:48 ` Hans Hagen [this message]
2017-07-24 19:34 ` Pablo Rodriguez
2017-07-24 8:54 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2015-02-22 17:37 Pablo Rodriguez
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
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=d878f631-1967-d332-1320-90e49a82de1c@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).