Hi, > I've made some tests and noticed that this only happens when using an > indexing engine. But looking at the code all seems fine. > > indexer.make_query is called with the second argument (require_all) as > True, which is the default, and according to the common indexer > specification: > @param require_all: boolean operator > (True -> AND (default) / False -> OR)
there are three code lines calling "make_query" in the function "indexsearch". As far as I understand, the first one (line 1019) evaluates the search text. It uses "OR". Later the search text query is ANDed with the filename query. I guess, the behaviour would change, if the "make_query" call in line 1019 would pass "True" instead of "False" as the second parameter. Could your (Aijin) try this, please? Would AND be the desired behaviour for the text search field? regards, Lars ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Translate-pootle mailing list Translate-pootle@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/translate-pootle
