You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@lucene.apache.org by Lance Norskog <go...@gmail.com> on 2007/09/14 22:01:03 UTC
UTF-8/unicode input in querying in Lucene
Hi-
The page http://lucene.apache.org/java/docs/queryparsersyntax.html does not
mention that \uNNNN Unicode syntax is supported.
For example, \u0048\u0045\u004c\u004c\u004f is HELLO.
Please add this to the page, it took experimentation to discover it.
Thanks,
Lance Norskog
Re: UTF-8/unicode input in querying in Lucene
Posted by Chris Hostetter <ho...@fucit.org>.
: > I don't believe the QueryParser actually treats \uNNNNN as a special
: > syntax
:
: LUCENE-716 added unicode escapes.
doh! that's what i get for assuming the random solr port i used to sanity
check my assumption was relatively up to date.
LUCENE-1000
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: UTF-8/unicode input in querying in Lucene
Posted by Yonik Seeley <yo...@apache.org>.
On 9/14/07, Chris Hostetter <ho...@fucit.org> wrote:
> I don't believe the QueryParser actually treats \uNNNNN as a special
> syntax
LUCENE-716 added unicode escapes.
-Yonik
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: UTF-8/unicode input in querying in Lucene
Posted by Chris Hostetter <ho...@fucit.org>.
: The page http://lucene.apache.org/java/docs/queryparsersyntax.html does not
: mention that \uNNNN Unicode syntax is supported.
: For example, \u0048\u0045\u004c\u004c\u004f is HELLO.
:
: Please add this to the page, it took experimentation to discover it.
I don't believe the QueryParser actually treats \uNNNNN as a special
syntax ... what you may have encountered was that when *javac* parses a
literal string constant, those sequences have special meaning -- but they
are already the literal unicode characters long before QueryParser sees
them.
As far as query parser is concerned the backslash in \uNNNNN is only
escaping the "u" (all characters can be escaped, wether they need it or
not)
-Hoss
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org