[
https://issues.apache.org/jira/browse/SOLR-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782701#action_12782701
]
Hoss Man commented on SOLR-412:
-------------------------------
Ok, i've become comvinced that we should do something like the psuedo-code Age
posted above ... not so much by the additional xslt-query-serialization
refrnece, but by thinking through the practical use cases...
* If a template specifies a charset in it's media-type property it doesnt'
change anything for those people
* If people have media-types w/o charset's but they do declare an encoding then
we're matching their wishes as best we can, and if they don't like it they can
add a charset to the media-type
Age: I haven't looked carefully at your patch, but if we can fix the double
charset problem you described (which should be easy with a simple substring
test) then i'm +1 for making this change.
> 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: Response Writers
> 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.
