On 02/23/2015 03:56 PM, Hans Hagen wrote:
> On 2/22/2015 6:37 PM, Pablo Rodriguez wrote:
>> [...]
>> 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?
> [...]
> \startxmlsetups xml:pre
>      \begingroup
>      \tt
>      \xmlflushspacewise{#1}
>      \endgroup
> \stopxmlsetups

Many thanks for your reply, Hans.

Your code works fine, but I forgot to mention another issue.

Here is another sample:

    \startbuffer[demo]
    <doc>
    <pre><code>for a &gt; b    &amp; c</code></pre>
    <pre class="tex"><code>\ConTeXt\ rocks!</code></pre>
    </doc>
    \stopbuffer

    \starttext

    \startxmlsetups xml:initialize
         \xmlsetsetup{#1}{doc}{xml:*}
         \xmlsetsetup{#1}{pre/code}{xml:pre}
         \xmlsetsetup{#1}{pre[@class='tex']/code}{xml:texcode}
    \stopxmlsetups

    \xmlregistersetup{xml:initialize}

    \startxmlsetups xml:doc
         \xmlflush{#1}
    \stopxmlsetups

    \startxmlsetups xml:pre
    \begingroup
      \tt
      \xmlflushspacewise{#1}
    \endgroup\par
    \stopxmlsetups

    \startxmlsetups xml:texcode
        \startΤΕΧ
            \xmlflushspacewise{#1}
        \stopTEX
    \stopxmlsetups

    \xmlprocessbuffer{main}{demo}{}

    \stoptext

And two questions:

Is there no way to get xml:texcode with a TEX typing?

Isn’t \xmlflushspacewise supposed to respect blank spaces? (Sorry, but I
don’t see any differences with \xmlflushlinewise.)

Many thanks for your help again,


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
___________________________________________________________________________________

Reply via email to