Excellent point about the saved queries. Thanks! So I could sniff the
locale (from the HTML page or the Java application,...) and infer the
"query language", or try to do automatic "guessing" of the language
based on the operator names (if they don't collide with indexed terms).
This brings up an other question: which query parser should I use? I
guess it would be a bad idea to invent one, it would be better to reuse
or adapt "the" query parser used by SOLR - or is it Lucene? Can you
point me to the parser?
Thanks,
Pierre
Walter Underwood a écrit :
I would do it in the client, even if it meant parsing the query,
modifying it, then unparsing it.
This is exactly like changing "To:" to "Zu:" in a mail header.
Show that in the client, but make it standard before it goes
onto the network.
If queries at the Solr/Lucene level are standard, then users
with different locale settings could share saved queries.
wunder
On 8/18/08 2:18 PM, "Pierre Auslaender" <[EMAIL PROTECTED]> wrote:
Would that be of any interest to the SOLR / Lucene community, given the
trend to globalisation / regionalisation ? My base is Switzerland - 4
official national tongues, none of them English.
If one were to localise the boolean operators, would that have to be at
the Lucene level, or could that be done at the SOLR level ?
Thanks,
Pierre
Otis Gospodnetic a écrit :
Hi,
Regarding Boolean operator localization -- there was a person who submitted
patches for the same functionality, but for Lucene's QueryParser. This was a
few years ago. I think his patch was never applied. Perhaps that helps.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
----- Original Message ----
From: Pierre Auslaender <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Saturday, August 16, 2008 12:50:53 PM
Subject: Localisation, faceting
Hello,
I have a couple of questions:
1/ Is it possible to localise query operator names without writing code?
For instance, I'd like to issue queries with French operator names, e.g.
ET (instead of AND), OU (instead of OR), etc.
2/ Is it possible for Solr to generate, in the XML response, the URLs or
complete queries for each facet in a faceted search?
Here's an example. Say my first query is :
http://localhost:8080/solr/select?q=bac&facet=true&facet.field=kind&facet.li
mit=-1
The "kind" field has three values: material, immaterial, time. I get
back something like this:
1024
27633
389
If I want to drill down into one facet, say into "material", I have to
"manually" rebuild a query like this:
http://localhost:8080/solr/select?q=bac&facet=true&facet.field=kind&facet.li
mit=-1&fq=kind:"material"
It's not too difficult, but surely Solr could add this URL or query
string under the "material" element. Is this possible? Or do I have to
XSLT the result myself?
Thanks,
Pierre Auslaender
