[
https://issues.apache.org/jira/browse/SOLR-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12779180#action_12779180
]
Hoss Man commented on SOLR-412:
-------------------------------
bq. IMHO the documentation in xslt 1.0 (http://www.w3.org/TR/xslt#output) is a
bit clearer on the usage of these fields
I'm not sure if looking at an *older* specification proposal is really the
right way to go here. Shouldn't the fact that all of that language was removed
from the XSLT 2.0 spec suggest that it was changed for a reason?
> 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
> Attachments: diff-2009-10-22
>
>
> 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.
