Dữ liệu của chúng tôi được phát hành theo nhiều giấy phép Cộng Đồng Sáng Tạo (Creative Commons) khác nhau.Thêm thông tin
Nếu bạn yêu thích nội dung này, vui lòng xem xét một khoản đóng góp .
Menu
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".
:-(
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
"
@Pandaa
There shouldn't be anything wrong with my search string: "saw him *ing" including the quotation marks. There's clearly a bug.
There's no bug. "wildcards are treated differently within quotes"
Try this: saw NEAR/1 him NEAR/1 *ing
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?
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.
It's still the same bug you reported some time ago:
https://tatoeba.org/eng/wall/sh...#message_30978