[
https://issues.apache.org/jira/browse/SOLR-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543249
]
Lance Norskog commented on SOLR-412:
------------------------------------
I am not an XSL expert. From what I can tell, the XSLT
documentation says that this:
<xsl:output method="xml" encoding="utf-8" />
<xsl:output media-type="text/xml; charset=UTF-8"
are equivalent. It seems like both should create XML
encoded in UTF-8, and should should create the same
Content-type header line. My bug report is that the
media-type form works, but that the method="xml" form
does not.
I would not be surprised to learn that the
method="xml" form does not do what it looks like; at
this point I have no respect for the XSLT language.
Thank you for your time and attention to my humble
complaint.
Lance
--- "Hoss Man (JIRA)" <[EMAIL PROTECTED]> wrote:
https://issues.apache.org/jira/browse/SOLR-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12542609
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
> 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.