clear
{{language.name}} No language found.
swap_horiz
{{language.name}} No language found.
search
Tatoeba coding event

In order to get more developers involved in Tatoeba and have some fun at the same time, we are organizing a coding event. If this sounds interesting, please fill up our survey.

Until then, if you wish to get involved, please read our guide for contributing as a developer or just contact us. We are an open source project and we welcome everyone!

DostKaplan DostKaplan December 19, 2018 at 2:06 AM December 19, 2018 at 2:06 AM link permalink

Bug...

English --> Turkish

I searched for "couldn't help crying" (including the quotes) and there was one result. I searched again with "couldn't help *ing" (including the quotes), and I got no results.

{{vm.hiddenReplies[30978] ? 'expand_more' : 'expand_less'}} hide replies show replies
CK CK December 19, 2018 at 2:20 AM, edited October 31, 2019 at 3:23 AM December 19, 2018 at 2:20 AM, edited October 31, 2019 at 3:23 AM link permalink

[not needed anymore- removed by CK]

{{vm.hiddenReplies[30979] ? 'expand_more' : 'expand_less'}} hide replies show replies
DostKaplan DostKaplan December 19, 2018 at 2:32 AM December 19, 2018 at 2:32 AM link permalink

That's not how it used to work. Without the quotes, the order of the words/pattern is not guaranteed.

{{vm.hiddenReplies[30980] ? 'expand_more' : 'expand_less'}} hide replies show replies
AlanF_US AlanF_US December 19, 2018 at 10:13 AM December 19, 2018 at 10:13 AM link permalink

I notice that this query (including the quotes) finds a result:

"couldn't help cry*"

However, it's not the search you wanted to perform. I did a web search (with terms like "sphinx wildcard quotes not working") to see whether anyone else has any insight on this, but didn't find anything relevant. @gillux, do you have any comment?

{{vm.hiddenReplies[30981] ? 'expand_more' : 'expand_less'}} hide replies show replies
DostKaplan DostKaplan December 19, 2018 at 12:51 PM December 19, 2018 at 12:51 PM link permalink

It was definitely working before, including "xxx yyy *zzz$".

{{vm.hiddenReplies[30983] ? 'expand_more' : 'expand_less'}} hide replies show replies
AlanF_US AlanF_US December 19, 2018 at 4:15 PM December 19, 2018 at 4:15 PM link permalink

When you say "before", what range of time are you talking about? @gillux or @TRANG, when's the last time the search engine or configuration changed?

{{vm.hiddenReplies[30988] ? 'expand_more' : 'expand_less'}} hide replies show replies
DostKaplan DostKaplan December 19, 2018 at 4:55 PM December 19, 2018 at 4:55 PM link permalink

@AlanF_US, I don't remember the range of time when this used to work, but I know I have searched (and needed to) this way before (with quotes). Do you guys log search requests? If so you should be able to see similar searches I have made in the past.

brauchinet brauchinet December 19, 2018 at 2:00 PM, edited December 19, 2018 at 2:29 PM December 19, 2018 at 2:00 PM, edited December 19, 2018 at 2:29 PM link permalink

I notice that a search like "Tom is *ing" (within quotes) only yields sentences where "is" and the ing-word are exactly one word apart.
It finds "Tom is very hardworking" "Tom is just trolling", even "Tom is drawing something" (because there's a second "ing"), but not "Tom is sleeping".

The documentation has the following example:
"Tom * * Mary * John"
This example finds sentences that have "Tom", then 2 words, then "Mary", then 1 word, and then "John."

This works only with quotes. Without quotes any number of words (including zero) can be between Tom and Mary.
So it seems wildcards are treated differently within quotes, and the issue is sort of an unwanted side-effect.

wolfgangth wolfgangth December 19, 2018 at 3:49 PM December 19, 2018 at 3:49 PM link permalink

I sometimes have this problem too, nothing is found;
if the "normale" search didn't find something try the "extended" search