Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: Unsupported encoding GB18030
From: =?iso-8859-1?Q?Jan_H=F8ydahl?= <jan.asf@cominvent.com>
In-Reply-To: <006f01cbf1d8$c2fecea0$48fc6be0$@thetaphi.de>
Date: Mon, 4 Apr 2011 13:36:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <069ACDB5-2111-4EE9-B2DD-61EB86A3DCA9@cominvent.com>
References: <8B74E207-BEB0-48D8-B0B0-9FFABD65806F@cominvent.com>
 <AANLkTimWD0b8GKB-AFUyoBBmuAOtmjHZS6wioRW6patE@mail.gmail.com>
 <AANLkTi=jJqws5H2aG1ptTS0QzD80_u5i8LGDsjg1HynA@mail.gmail.com>
 <AANLkTinv=BupXzC0A28u7H7qqRif3u=RQMJB8NPxKz3v@mail.gmail.com>
 <00b101cbf07f$47ded5d0$d79c8170$@thetaphi.de>
 <AANLkTikKTsjjJhNn8A3crNeTKOLmzOvz9bxXC13LEwXa@mail.gmail.com>
 <50DD86CF-7694-4CE4-BCC7-7313A0C6003C@cominvent.com>
 <alpine.DEB.2.00.1104021550160.25634@bester>
 <006f01cbf1d8$c2fecea0$48fc6be0$@thetaphi.de>
To: dev@lucene.apache.org

>>> : I don't see the reason why "exampledocs" should contain docs with =
narrow
>>> charsets not guaranteed to be supported.
>> personally i would like to see us add a lot more exampledocs in a lot =
more
>> esoteric encodings, precisely to help end users sanity test this sort =
of
>> we frequetnly get questions form people about character encoding
>> wonkiness, and things like test_utf8.sh, utf8-example.xml, and now
>> gb18030-example.xml can help us narrow down the problem: their client
>> code, their servlet container, or solr?
>=20
> Same here. In my opinion, an example set of files should also contain =
"more
> complicated" ones to show what Solr can do. If some of them don't =
work, it's
> not really a problem. Maybe we should simply add a "tag" to the =
filename to
> mark them as not working in every configuration.

Positive to more example docs!

My concern was that since indexing exampledocs/*.xml is perhaps THE most =
common action any new Solr user will do, it should just work, and it's a =
benefit if the results revolve around the same theme, a set of products =
with category and prices. We definitely want to show off more advanced =
features, and we should add more example documents for that. Plain test =
docs could be placed in a a subfolder "exampledocs/extras" or something.

Regarding the WindowsXP VMmware I was using, it had a Sun JRE (not JDK) =
which was auto-updated from 1.5 to 1.6.
After completely uninstalling Java and re-installing =
jdk-6u24-windows-i586.exe the GB18030 encoding is supported.

--
Jan H=F8ydahl, search solution architect
Cominvent AS - www.cominvent.com


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