escape lucene key words so that it can parse the string

Better still, we should find a way of escaping strings (ie keywords and special characters) so that Lucene will be able to parse the query.

There is no other information available when this happens. Only the text itself. If we want we could pass those information from the GWT client but given that we will be focusing more on the new editor I will not make the change.

There is no other information available when this happens. Only the text itself. If we want we could pass those information from the GWT client but given that we will be focusing more on the new editor I will not make the change.

That's our excuse for so many things, and yet the new editor is still not ready!

Anyway, fair enough, but please add a prominent comment to the relevant GWT service, so that, when we port that code to a REST service for the new editor, we can be sure to add the extra context info there. (In fact, when searching based on TextFlow content, we shouldn't even pass the (potentially bulky) text itself, because the server can get it if we just pass the textflow id.)