Lists Home |
Date Index |
- From: John Cowan <firstname.lastname@example.org>
- To: XML Dev <email@example.com>
- Date: Wed, 12 May 1999 13:05:47 -0400
Nik O wrote:
> I should have mentioned that i had previously tried to include entity
> declarations within my document (there is presently no DTD associated with
> the document).
That is your problem. You need to create a DTD internal subset
declaration, like this:
<!DOCTYPE root-element-name [
<!ENTITY copy "&copy;">
<!ENTITY aelig "&aelig;">
That will cause the entity reference "æ" to expand to the
string "æ", which seems to be what you want.
> John Cowan wrote:
> > All you actually have to do is to ensure that the next character
> > (if not #, see above) is a NAMESTRT character, and that all characters
> > until ; are either NAME or NAMESTRT characters. There is no need (and
> > in fact it is forbidden) to look up the supposed entity name anywhere.
I was talking about a different case: entity references within
entity declarations, not entity references within the document instance
itself. This is really only of concern to parser writers.
John Cowan http://www.ccil.org/~cowan firstname.lastname@example.org
You tollerday donsk? N. You tolkatiff scowegian? Nn.
You spigotty anglease? Nnn. You phonio saxo? Nnnn.
Clear all so! 'Tis a Jute.... (Finnegans Wake 16.5)
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)