From: Kate F <kate@elide.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TeX in \xmlsetentity and DTDs in DOCTYPEs
Date: Mon, 18 Jan 2016 20:49:34 +0000 [thread overview]
Message-ID: <CAA36g0W=akX5YCb7-B8=CyoHvGc=iDrAM5WNy_tqkWrcUkcmjg@mail.gmail.com> (raw)
In-Reply-To: <569D3944.4030804@wxs.nl>
On 18 January 2016 at 19:13, Hans Hagen <pragma@wxs.nl> wrote:
> On 1/18/2016 5:22 PM, Kate F wrote:
>>
>> On 18 January 2016 at 13:30, Thomas A. Schmitz
>> <thomas.schmitz@uni-bonn.de> wrote:
>>>
>>> On 01/17/2016 07:24 PM, Hans Hagen wrote:
>>>>
>>>>
>>>> it should work in the in beta now
>>>
>>>
>>>
>>> Hi Hans,
>>>
>>> now I have a problem :-) What should take precedence if an entity is both
>>> defined in the dtd and as a \xmltexentity? The way I see it, the latter:
>>> e.g., in the DTD, I might declare something for use in a browser but
>>> require
>>> a different solution when typesetting with ConTeXt. The latest and
>>> greatest
>>> now takes my DTD definitions instead of the \xmltexentities, which did
>>> not
>>> happen before. Is that an unwanted side effect or the new default?
>>>
>>
>> Ah, there's a bug:
>>
>> <!ENTITY i.opt "<option>-i</option>">
>>
>> This should produce an <option> node in the DOM tree, just as if you'd
>> typed that out where the entity is used. Currently ConTeXt takes that
>> as literal text, as if you'd typed "<option>-i<option/>"
>>
>> Often I wish XML weren't so complex...
>
>
> are you sure? i've never seen that
>
> Hans
Yep!
These are called "internal parsed entities". "Parsed" requires that
any tags *inside* the entity must be balanced, unlike in SGML
entities.
Sorry I can't find a clear explanation in the XML spec; it's a pretty
confusing document.
But here's some random person's slide illustrating an example:
http://images.slideplayer.com/23/6622270/slides/slide_47.jpg
libxml2 deals with these correctly, which is what I've been using
(xsltproc and friends) for my documents which use them. I generally
trust libxml2 to get things right.
I use these entities to centralise often-repeated fragments between
documents, kind of like how you might use a primitive macro in TeX.
So for example in one external DTD I have some general things:
<!ENTITY macro.arg "<replaceable>macro</replaceable>">
<!ENTITY equal.lit "<literal>=</literal>">
And then in one specific document's internal entities, something which
uses them:
<!ENTITY D2.opt
"<option>-D</option>¯o.arg;&equal.lit;<replaceable>defn</replaceable>">
Then if I change my mind about how I want to mark up "=", for example,
I only have one place to change it. This makes life with XML a little
bit less painful.
--
Kate
___________________________________________________________________________________
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-18 20:49 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
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 [this message]
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='CAA36g0W=akX5YCb7-B8=CyoHvGc=iDrAM5WNy_tqkWrcUkcmjg@mail.gmail.com' \
--to=kate@elide.org \
--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).