[
https://issues.apache.org/jira/browse/SOLR-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545160
]
Hoss Man commented on SOLR-412:
-------------------------------
based on my reading of: http://www.w3.org/TR/xslt20/#element-output
the "method" attribute exists solely to instruct the transformer how to
generate the output ... it appears to exist largely to support hacks for html
but also to support plain text output.
"encoding" dictates the actual character encoding used in the output stream.
"media-type" is ... the media-type, which if unspecified defaults to either
"text/xml" if method="xml" or "text/html" or "text/plain" for the corrisponding
methods ... but the default media-type does not ever seem to be influenced by
the "encoding" attribute.
I'm not convinced there isn't *something* Solr can do to handle this situation
better, i just don't know what it is.
> XsltWriter does not output UTF-8 by default
> -------------------------------------------
>
> Key: SOLR-412
> URL: https://issues.apache.org/jira/browse/SOLR-412
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 1.2
> Environment: Tomcat 5.5
> Linux Red Hat ES4 (2.6.9-5.ELsmp from 'uname -a')
> Reporter: Lance Norskog
>
> XsltWriter outputs XML text in ISO-8859-1 encoding by default.
> Tomcat 5.5 has URIEncoding="UTF-8" set in the <Connector> element as
> described in the Wiki.
> This outout description in the XML:
> <xsl:output method="xml" encoding="utf-8" />
> gives output with this header:
> HTTP/1.1 200 OK
> Server: Apache-Coyote/1.1
> Content-Type: text/xml;charset=ISO-8859-1
> Transfer-Encoding: chunked
> Date: Wed, 14 Nov 2007 17:49:11 GMT
> I had to change the <xsl:output> directive to this:
> <xsl:output media-type="text/xml; charset=UTF-8" encoding="UTF-8"/>
> This is the root cause of SOLR-233.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
