Content Pipeline Guide > Customizing Publishing > Configuring Character Entity Substitution Files for HTML Publishing > Substitutions Involving Strings
  
Substitutions Involving Strings
Following are examples of string substitutions:
<character-mapping>
<unicode char="8658" string="=&gt;"/>
<unicode char="8656" string="&lt;="/>
<unicode char="8594" string="-&gt;"/>
<unicode char="8592" string="&lt;-"/>
<unicode char="402" string="f"/>
<unicode char="8230" string="..."/>
<unicode char="352" string="S"/>
<unicode char="8249" string="&lt;"/>
<unicode char="338" string="OE"/>
<unicode char="8216" string="'"/>
<unicode char="8217" string="'"/>
<unicode char="8220" string="&amp;quot;"/>
<unicode char="8221" string="&amp;quot;"/>
<unicode char="8226" string="."/>
<unicode char="8211" string="-"/>
<unicode char="8212" string="--"/>
<unicode char="732" string="~"/>
<unicode char="8482" string="(TM)"/>
<unicode char="353" string="s"/>
<unicode char="8250" string="&gt;"/>
<unicode char="339" string="oe"/>
<unicode char="376" string="Y"/>
<unicode char="8194" string=" "/>
<unicode char="8195" string=" "/>
</character-mapping>
The string attribute value is read by an XML parser, so entity references beginning with an ampersand (&) are resolved to form a character. For example “=&gt;” is parsed and substituted as “=>”, and “&amp;quot;” is parsed and substituted as “&quot;”.