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 21:20:55 +0100 [thread overview]
Message-ID: <569954A7.4000900@uni-bonn.de> (raw)
In-Reply-To: <CAA36g0UyE3KjdeCqTwQh7S5R3RRpnNc6JaNa-qsaJWBdz7gbCA@mail.gmail.com>
On 01/15/2016 06:58 PM, Kate F wrote:
> So I see! But many DTDs contain definitions for entities, which I
> would like to use, rather than repeating those definitions by
> \xmlsetentity in ConTeXt. Some XML documents also have their own
> document-specific entities inside the DOCTYPE at the top of the file.
>
> For example in legal agreements, I have something like:
>
> <?xml version="1.0"?>
> <!DOCTYPE blah SYSTEM "blah.dtd" [
> <!ENTITY us "the company">
> <!ENTITY you "the customer">
> ]>
>
> Where the stuff inside [...] is considered part of a document-specific DTD.
> libxml2 handles this sort of thing with its "dtdattr" options; I
> presume lxml has something similar.
AFAIK, ConTeXt has its own xml parser based on lua lpeg, see file
lxml-tab.lua. There is code there that treats entities, but I have never
used this approach, so you'll probably have to wait till Hans looks at
your question (or understand the lua code...)
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 20:20 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
2016-01-15 17:58 ` Kate F
2016-01-15 20:20 ` Thomas A. Schmitz [this message]
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=569954A7.4000900@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).