Can the rule to generate META HTTP-EQUIV be relaxed

Hi, In the current XSLT spec for the HTML output method, the line 
<META HTTP-EQUIV='Content-Type' CONTENT='text/html; charset=UTF-8'>
with charset specifiable via <xsl:output encoding="some-string" />

However, this does not allow the encoding to be parameterised and in
cases where one desires a single XSL to generate multiple HTML files
with different encodings [iso-8859-1, big5 (Traditional Chinese) ,
gb2312 (Simplified Chinese)]

Is there a need to force the above META string into the target tree
and hence be serialized. Why not let the XSL author decide what
encoding is appropiate for the target tree. Something like the
following might also be appropiate

<xsl:param name="enc" select="'iso-8859-1'"/>
<xsl:output encoding="$enc" />

Regards, Yusuf

-- 
Yusuf Goolamabbas
yusufg@outblaze.com