I am not an XML Spy user. (I have heard that XML Spy does have some
character set issues.)
However, I can tell you something about character entities (Numeric
Character Reference) that might help.
The entity and the document type are different issues, but they come
together since your character is going to be in a particular document
In SGML and HTML you can use & eacute;. This is a legal character
reference. But SGML will not display in a browser. HTML will display
in a browser, given the document tags conform to HTML tag set (SGML
will be a blank screen).
In SGML you can use the hex NCR (& #x00E8;) or dec NCR (& #232;). The
document will validate. But you cannot see the SGML in a browser. If
you do find software that does display SGML, it might not respect the
NCR, but will probably respect the glyphs (non-number character
In HTML you must give a character set to see the hex NCR. Otherwise
it will display goofy. Example of the meta tag:
META HTTP-EQUIV="Content-Type" CONTENT="text/html;charset=utf-8"
In XML there will not be a problem with the NCR, but the & eacute;
references will not be legal. IE will give you error messages when it
trys to display the XML. The only way to get these & eacute;
characters in your XML is to have a DTD that includes them. Or you
could have them as ENTITY declarations in your XML DOCTYPE subset.
James Clark's SP is nice in this respect. His SX converts your SGML
to XML. The nice thing is that he takes care of all this. All your
NCR and non-numeric character references are converted to raw
unicode. They will appear in your text editor as strange looking
stuff. But just open your XML in IE and your in business. Like magic,
no more problems with invalid characters. The conversion tool
defaults to utf-8, but you can set it to different character sets.
Well, that is heady enough. I am not sure what your workflow is like,
so I will leave it at that.
Library of Congress
--- "Jane E. Stevenson" <[log in to unmask]> wrote:
> Hello all,
> As someone pretty new to working with EAD, I hope that someone will
> be able
> to clarify my confusion about displaying special characters, such
> as e with
> acute accent or u with an umlaut.
> Is it the case that if I create an EAD file using entities in the
> form of
> é rather than the Unicode format of é then there is
> no way I
> can get them to display in Internet Explorer?
> I know that XML uses Unicode, so I can see that using the decimal
> number is
> correct for XML. However, I'm using XMLSPY, and this lists the
> entities as ISO entities. It seems odd that XMLSPY, an editor for
> documents, uses these when they don't display in a browser.
> I see that a number of people reading this list use XMLSPY, and I'm
> someone can confirm to me whether it is the case that I can't use
> facility in XMLSPY for adding special characters if I want the
> document to
> display in the browser?
> With thanks,
> Jane Stevenson
> Archives Hub
> University of Manchester
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.