From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TeX in \xmlsetentity and DTDs in DOCTYPEs
Date: Fri, 15 Jan 2016 18:34:13 +0100 [thread overview]
Message-ID: <56992D95.2060501@uni-bonn.de> (raw)
In-Reply-To: <CAA36g0VMu=FSCDtNxWfLUxeEmnmHfxGeKmXS-SEY5W=Y0ND+cQ@mail.gmail.com>
On 01/15/2016 06:21 PM, Kate F wrote:
> Hi. I'm using MkIV's XML stuff. I have two related questions.
>
> Firstly, can I have entities in XML expand out to TeX markup?
>
> I thought this was how you'd do it, but this produces a document that
> says literally "xxx~yyy\thinspace zzz", whereas I want the ~ and
> \thinspace to be executed as TeX commands. Test case below.
>
> Secondly, is it possible to have ConTeXt load such entities from a
> DTD? If I use a DOCTYPE in my XML, entities from that DTD seem to not
> be loaded.
What do you mean? The way ConText processes entities is completely
independent from your DTD.
> Thanks.
>
> a.xml:
> <?xml version="1.0"?>
> <a>xxx yyy zzz</a>
>
> a.tex:
> \startxmlsetups xml:mysetups
> \xmlsetsetup{\xmldocument}{a}{xml:*}
> \stopxmlsetups
> \xmlregistersetup{xml:mysetups}
>
> \startxmlsetups xml:a
> \xmlflush{#1}
> \stopxmlsetups
\enabledirectives[lxml.escapedentities]
\xmltexentity{nbsp}{~}
\xmltexentity{thinsp}{\thinspace}
> \xmlsetentity{nbsp}{~}
> \xmlsetentity{thinsp}{\thinspace}
>
> \starttext
> \xmlprocessfile{main}{a.xml}{}
> \stoptext
Thomas
___________________________________________________________________________________
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 prev parent reply other threads:[~2016-01-15 17:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 17:21 Kate F
2016-01-15 17:34 ` Thomas A. Schmitz [this message]
2016-01-15 17:58 ` Kate F
2016-01-15 20:20 ` Thomas A. Schmitz
2016-01-16 0:33 ` Hans Hagen
2016-01-16 15:55 ` Kate F
2016-01-17 18:24 ` Hans Hagen
2016-01-18 13:30 ` Thomas A. Schmitz
2016-01-18 16:13 ` Kate F
2016-01-18 16:22 ` Kate F
2016-01-18 19:13 ` Hans Hagen
2016-01-18 20:49 ` Kate F
2016-01-18 21:16 ` Hans Hagen
2016-01-19 2:16 ` Kate F
2016-01-19 2:39 ` Kate F
2016-01-18 20:07 ` Hans Hagen
2016-01-18 20:56 ` Kate F
2016-01-18 21:19 ` Hans Hagen
2016-01-18 21:26 ` Hans Hagen
2016-01-18 21:45 ` Thomas A. Schmitz
2016-01-19 8:19 ` 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=56992D95.2060501@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).