menu
Tatoeba
language
Register Log in
language English
menu
Tatoeba

chevron_right Register

chevron_right Log in

Browse

chevron_right Show random sentence

chevron_right Browse by language

chevron_right Browse by list

chevron_right Browse by tag

chevron_right Browse audio

Community

chevron_right Wall

chevron_right List of all members

chevron_right Languages of members

chevron_right Native speakers

search
clear
swap_horiz
search
DostKaplan DostKaplan February 4, 2020, edited February 4, 2020 February 4, 2020 at 5:03:49 PM UTC, edited February 4, 2020 at 5:04:47 PM UTC link Permalink

Search string: "saw him run" (including the quotation marks)
URL: https://tatoeba.org/eng/sentenc...rom=eng&to=tur

3 results:

I saw him running.
I saw him run away.
I saw him running away.

I then changed the search string to: "saw him *ing"
URL: https://tatoeba.org/eng/sentenc...rom=eng&to=tur

The results did NOT include the two sentences containing "running" above. Instead the results had sentences like "I saw him ... morning".

:-(

{{vm.hiddenReplies[34102] ? 'expand_more' : 'expand_less'}} hide replies show replies
Pandaa Pandaa February 4, 2020, edited February 4, 2020 February 4, 2020 at 5:31:02 PM UTC, edited February 4, 2020 at 6:00:06 PM UTC link Permalink

Use this: https://tatoeba.org/eng/sentenc...&sort_reverse=

"
This example finds English sentences that have "Tom", then two words, then "Mary", then one word, and then "John."

"Tom * * Mary * John"

This example finds English sentences that have words beginning with "red", including the word "red".

red*

This example finds English sentences that have words ending with "red", including the word "red".

*red
"

{{vm.hiddenReplies[34103] ? 'expand_more' : 'expand_less'}} hide replies show replies
DostKaplan DostKaplan February 4, 2020 February 4, 2020 at 7:25:55 PM UTC link Permalink

@Pandaa
There shouldn't be anything wrong with my search string: "saw him *ing" including the quotation marks. There's clearly a bug.

{{vm.hiddenReplies[34109] ? 'expand_more' : 'expand_less'}} hide replies show replies
Pandaa Pandaa February 4, 2020, edited February 4, 2020 February 4, 2020 at 8:56:32 PM UTC, edited February 4, 2020 at 9:07:09 PM UTC link Permalink

There's no bug. "wildcards are treated differently within quotes"

Try this: saw NEAR/1 him NEAR/1 *ing

{{vm.hiddenReplies[34111] ? 'expand_more' : 'expand_less'}} hide replies show replies
DostKaplan DostKaplan February 4, 2020 February 4, 2020 at 9:28:29 PM UTC link Permalink

This NEAR/1 shit is laughable. Who searches like this? This is so f'd up. Can't we just revert to the old (4 years ago??) search function which is more intuitive?

{{vm.hiddenReplies[34112] ? 'expand_more' : 'expand_less'}} hide replies show replies
gillux gillux February 6, 2020 February 6, 2020 at 8:37:29 AM UTC link Permalink

Since we use Manticore as a search engine, the search syntax is defined by them. Among intuitive features like the wildcard, Manticore includes less intuitive things like the NEAR operator.

We have been using Manticore (or Sphinx, as it was named before) for many years. We didn’t change anything in the way the search behave. Can you confirm that 4 years ago, searching for "saw him *ing" behave differently? Maybe something changed in newer versions of Manticore.

brauchinet brauchinet February 4, 2020, edited February 4, 2020 February 4, 2020 at 5:39:54 PM UTC, edited February 4, 2020 at 5:41:08 PM UTC link Permalink

It's still the same bug you reported some time ago:
https://tatoeba.org/eng/wall/sh...#message_30978