Yes, you can declare each field with the Spanish, French, etc. types.
The _t and other types are dynamic and don't have to be declared. This
feature is generally used when you have hundreds or thousands of fields.
It is more clear to declare your fields.
You're right- that error should not be
Hi Erick, thanks for your help!
I need some technical help though... let me put it that way:
1. I deleted everything in index with:
curl http://localhost:8983/solr/update -F stream.body='
deletequery*:*/query/delete'
curl http://localhost:8983/solr/update -F stream.body=' commit /'
2. I created
Thre's approximately a 100% chance that you are going to go through a server
side langauge(php, ruby, pearl, java, VB/asp/,net[cough,cough]), before you get
to Solr/Lucene. I'd recommend it anyway.
This code will should look at the user's browser locale (en_US, pl_PL, es_CO,
etc). The server
2010/10/20 Dennis Gearon gear...@sbcglobal.net
Thre's approximately a 100% chance that you are going to go through a
server side langauge(php, ruby, pearl, java, VB/asp/,net[cough,cough]),
before you get to Solr/Lucene. I'd recommend it anyway.
I use a server side language (Ruby) as I build
Here's what I would do -
Search all the fields everytime regardless of language. Use one handler and
specify all of these in qf and pf.
question_en, answer_en,
question_fr, answer_fr,
question_pl, answer_pl
Individual field based analyzers will take care of appropriate tokenization
and you will
See below:
But also search the archives for multilanguage, this topic has been
discussed
many times before. Lucid Imagination maintains a Solr-powered (of course)
searchable
list at: http://www.lucidimagination.com/search/
http://www.lucidimagination.com/search/
On Wed, Oct 20, 2010 at 9:03 AM,
