This is an artifact resulting from XSLT being used to effect the transform.
Entity references are resolved by XML parsers by design. In short I would
not be concerned about the resolution of you character entity references
since these can easily be transcoded to other values. xmllint (part of
libmxl <http://xmlsoft.org/>), for example, will move you between UTF8 and
ASCII, amongst other encodings. There are mechanisms available to preserve
text values in an input file in the output file of an XSLT transformation,
but use of them can get very messy since they effectively allow for the
inclusion of non-XML character data.
Any custom entities that you have written and included in your file for
such boilerplate text as, say, your repository address, will also be
resolved, and xmllint is going to be of no use here.
Hope that helps soothe the nerves,
Yale University Library
At 01:48 PM 5/25/2004, Betsy Pittman wrote:
>I noticed that in converting our EAD v1 finding aids to
>EAD2002 all the entity coding
>was converted from Hex to HTML. Am I worrying
>needlessly about the longevity of/support for the
>HTML symbols and diacritics?
> Curator for Political and Connecticut History Collections
>Archives & Special Collections at the
> Thomas J. Dodd Research Center
>University of Connecticut
>405 Babbidge Road, Unit 1205
>Storrs, CT 06269-1205
>Voice (860) 486.4507
>FAX (860) 486.4521
>[log in to unmask]