-<dd><p>That depends entirely on libxml2. mod_proxy_html supports
-charset detection, but does not itself support any charsets.
-It works by passing the charset detected to libxml2 when it sets
-up the parser.</p>
-<p>This means that mod_proxy_html inherits its charset support
-from libxml2, and will always support <em>exactly</em> the same
-charsets available in the version of libxml2 you have installed.
-So bug the libxml2 folks, not us!</p>
-<p class="v3">In Version 3, charset support is much expanded provided
-<code>ProxyHTMLMeta</code> is enabled, and any charset can be supported
-by aliasing it with <code>ProxyHTMLCharsetAlias</code>.</p>
+<dd><p>In version 2, that depends entirely on libxml2, and your charset
+is supported if and only if libxml2 supports it.</p>
+<p>In Version 3.1, charset support is much expanded provided
+<a href="../mod_xml2enc/">mod_xml2enc</a> is enabled. It is normally
+sufficient just to load mod_xml2enc: it will be configured automatically
+if you configure mod_proxy_html using <code>ProxyHTMLEnable</code>.
+In a few cases, you may need to customise charset support further using
+mod_xml2enc's directives.</p>
+<p>Note that some servers send inconsistent and even conflicting charset
+information, and may generate unexpected results. Setting
+<code>ProxyHTMLMeta On</code> may help resolve such cases, and will
+help diagnose problems with extra debug information in the error log.</p>