Hi Chris, Gora
thanks for the help. I am indeed writing a client conversing with solr with
http get calls.
Using your suggestions (in particular the echoParams tip) I managed to find
the problem.
Curiously it turns out that on sending messages I should not convert to
Utf8 or otherwise and on receiving one has to. NOt sure if this is a Qt
oddity but things seem to be fine now.
Thanks again,
Roland.
Chris Hostetter wrote:
: Programming in C++ (Using Qt's QString) I am wondering what conversion to
: apply before compiling words with such letters into the solrquery.
if you are implementing your own client and talking to Solr via HTTP then
how you escape/encode characters in URLs is largely dependent on how you
have your servlet container configured.
For example...
https://wiki.apache.org/solr/FAQ#Why_don.27t_International_Characters_Work.3F
https://wiki.apache.org/solr/SolrTomcat#URI_Charset_Config
One way to help debug what is going on is to use "echoParams=all" in your
request, and then look at the "requestHeader" section of the response.
that will echo back *exactly* what solr got from the servlet container for
each of your input params. If you use it with the python response writer
(wt=python) you will see escape sequences for any non-ascii characters --
which can be helpful for verifying the problem is in how the utf8 input is
parsed, and not in how it is being returned to your client
there is also an "example/exampledocs/test_utf8.sh" that is helpful for
sanity checking these sorts of things independent of your client code.
-Hoss
