26

I am trying to set the innerxml of a xmldoc but get the exception: Reference to undeclared entity

XmlDocument xmldoc = new XmlDocument();
string text = "Hello, I am text α   – —"
xmldoc.InnerXml = "<p>" + text + "</p>";

This throws the exception:

Reference to undeclared entity 'alpha'. Line 2, position 2..

How would I go about solving this problem?

marc_s
  • 732,580
  • 175
  • 1,330
  • 1,459
Rob
  • 1,163
  • 2
  • 18
  • 28

9 Answers9

30

XML, unlike HTML does not define entities (ie named references to UNICODE characters) so &alpha; &mdash; etc. are not translated to their corresponding character. You must use the numerical value instead. You can only use &lt; and &amp; in XML

If you want to create HTML, use an HtmlDocument instead.

Stephan Leclercq
  • 893
  • 7
  • 11
  • 2
    HtmlDocument comes from the System.Windows.Forms namespace http://j.mp/pSmv82 If you don't like its close association with the WebBrowser control or that causes issues to your app, a pure HTML parser is available through the HTML Agility Pack http://htmlagilitypack.codeplex.com/wikipage?title=Examples – John K Aug 03 '11 at 23:59
15

In .Net, you can use the System.Xml.XmlConvert class:

string text = XmlConvert.EncodeName("Hello &alpha;");

Alternatively, you can declare the entities locally by putting the declarations between square brackets in a DOCTYPE declaration. Add the following header to your xml:

<!DOCTYPE documentElement[
<!ENTITY Alpha "&#913;">
<!ENTITY ndash "&#8211;">
<!ENTITY mdash "&#8212;">
]>

Do a google on "html character entities" for the entity definitions.

LandedGently
  • 693
  • 1
  • 8
  • 16
7

Try replacing &Alpha with 

  &#913;
FlySwat
  • 172,459
  • 74
  • 246
  • 311
6

The preceding answer is right. Another alternative is to link your html document to the DTD where those character entities are defined, and that is standard XHTML DTD definition. Your xml file should include the following declaration:

 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
            "http://www.w3.org/TR/html4/strict.dtd">
Fernando Miguélez
  • 11,196
  • 6
  • 36
  • 54
3

Use string System.Net.WebUtility.HtmlDecode(string) which will decode all HTML entity encoded characters to its Unicode variant. It is available from dot.net framework 4

verbedr
  • 1,784
  • 1
  • 15
  • 18
  • if you have an `&` in your HtmlDecode will mess it up b/c it will turn it into `&` and then XML will choke on it – BlackICE Sep 06 '22 at 19:53
1

A variant of the solution described at https://stackoverflow.com/a/842836/15178054 is: Declare the entities in a separate file, and then reference that file from the XML declaration subset. Here is an example for how to use HTML entities in an XSLT stylesheet.

<!DOCTYPE xsl:stylesheet
[
<!ENTITY % htmlentities SYSTEM "html-entity-list.ent">
%htmlentities;
]>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"...>

The external file with entities is "html-entitiy-list.ent". I have generated it from https://html.spec.whatwg.org/entities.json . An example entry in the generated file is this one:

<!ENTITY Auml "Ä">
Felix Sasaki
  • 11
  • 1
0

The use of a HtmlDocument wasn't suitable in my situation, our system had a custom XmlUrlResolver which we made use of for loading the xml.

//setup
public class CustomXmlResolver : XmlUrlResolver { /* ... */ }
String originalXml; //fetched xml with html entities in it

var doc = new XmlDocument();
doc.XmlResolver = new AdCastXmlResolver();

//making use of a transitional dtd
doc.LoadXml("<!DOCTYPE html SYSTEM \"xhtml1-transitional.dtd\" > " + originalXml);
Nick Josevski
  • 4,156
  • 3
  • 43
  • 63
0

You could also set the InnerText to "Hello, I am text α – —", making the XmlDocument escape them automatically. I think.

configurator
  • 40,828
  • 14
  • 81
  • 115
0

If you do want to use the HTML entity names you are used to, the W3C has got you covered and has produced "XML Entity Definitions for Characters" http://www.w3.org/TR/xml-entity-names/, which essentially is a list of named entities very similar to the ones that HTML has. But as mentioned above, this is not built into XML, and needs to be explicitly supported by XML applications that want to use these named entities.

dret
  • 531
  • 3
  • 7