lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Age Jan Kuperus (JIRA)" <>
Subject [jira] Commented: (SOLR-412) XsltWriter does not output UTF-8 by default
Date Thu, 19 Nov 2009 21:45:39 GMT


Age Jan Kuperus commented on SOLR-412:

I agree. Although I was pretty sure XSLT 2.0 was even stricter but could not immediately find
a formal reference.
So I did some more research today and found the following confirmation in,
which is part of XSLT 2.0:

"media-type 	A string of Unicode characters specifying the media type (MIME content type)
[RFC2046]; the charset parameter of the media type MUST NOT be specified explicitly in the
value of the media-type parameter".

Therefore I would like you to have a look at my patch and comment on it (or even commit it
;-). Committing this patch would also require the patches for SOLR-233 and SOLR-514  to be
undone (as their results are illegal in both XSLT 1.0 and 2.0), and possibly has documentation

> XsltWriter does not output UTF-8 by default
> -------------------------------------------
>                 Key: SOLR-412
>                 URL:
>             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.

View raw message