lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yonik Seeley <yo...@lucidimagination.com>
Subject Re: Unsupported encoding GB18030
Date Fri, 01 Apr 2011 14:20:49 GMT
On Fri, Apr 1, 2011 at 10:07 AM, Robert Muir <rcmuir@gmail.com> wrote:
> On Fri, Apr 1, 2011 at 10:00 AM, Yonik Seeley
> <yonik@lucidimagination.com> wrote:
>> On Fri, Apr 1, 2011 at 9:22 AM, Jan H√łydahl <jan.asf@cominvent.com> wrote:
>>> Testing the new Solr 3.1 release under Windows XP and Java 1.6.0_23
>>>
>>> When trying to post example\exampledocs\gb18030-example.xml using post.jar I
get this error:
>>> % java -jar post.jar gb18030-example.xml
>>> jar gb18030-example.xml
>>> SimplePostTool: version 1.3
>>> SimplePostTool: POSTing files to http://localhost:8983/solr/update..
>>> SimplePostTool: POSTing file gb18030-example.xml
>>> SimplePostTool: FATAL: Solr returned an error #400 Unsupported encoding: GB18030lap
>>>
>>> From the stack it is caused by com.ctc.wstx.exc.WstxIOException: Unsupported
encoding: GB18030
>>>
>>> The same works on my MacBook with Java1.6.0_24
>>
>> Interesting - things seem fine for me on Win7 Java1.6.0_24, but I
>> don't have XP around any longer to see if that's the factor somehow.
>>
>
> Its worth mentioning, there is no guarantee the JRE will support
> GB18030 encoding.
>
> There are only 6 charsets guaranteed to exist:
> http://download.oracle.com/javase/6/docs/api/java/nio/charset/Charset.html

Indexing *.xml is a very common thing for new users to do.
If this is likely to fail for enough users, we should move, remove, or
at least change the filename to
something like gb18030-example.xml.gb18030 so it won't get picked up
by accident.

-Yonik
http://www.lucenerevolution.org -- Lucene/Solr User Conference, May
25-26, San Francisco

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message