Is there anyway to use the old wildcards * & @?
Wildcards * & @?
- Thread starter ACardiganAndAFrown
- Start date
? is good. Not sure * is working?
Perhaps I didn't toggle enough, but when looking for 举一反三 for instance - I tried:
*三
(* = ???, correct?)
The first result I keep getting is Italian for some reason:
Toggling off of Italian takes me to full-text English:
Then Cantonese:
Then French:
And then German...etc.
Yet the * function doesn't really seem to work as it should, I'm seeing a lot of results starting with "三" rather than "???三".
A lot of results are also automatically full-text queries. That also seem strange with in the search parameters. I would assume that C-E results are priority unless otherwise specified. Yet toggling around to Chinese-English seemed to be quite cumbersome.
=====
Not a great example, I admit. But it was one I was legitimately trying to search "in the wild."
*三
(* = ???, correct?)
The first result I keep getting is Italian for some reason:
Toggling off of Italian takes me to full-text English:
Then Cantonese:
Then French:
And then German...etc.
Yet the * function doesn't really seem to work as it should, I'm seeing a lot of results starting with "三" rather than "???三".
A lot of results are also automatically full-text queries. That also seem strange with in the search parameters. I would assume that C-E results are priority unless otherwise specified. Yet toggling around to Chinese-English seemed to be quite cumbersome.
=====
Not a great example, I admit. But it was one I was legitimately trying to search "in the wild."
Well * can be any number of characters, including zero, so seeing results starting with 三 isn't wrong here; if you want at least one other character before it you'd want to enter *? or ?*. That at least is consistent with the old app.
As far as full-text searches: the problem is that inline Chinese in a lot of dictionaries isn't tagged as Chinese and so the system is still indexing it as English (or Italian or German or whatever). We should probably just add a little check for now to exclude anything containing Chinese characters from those other search profiles, but it's doing those full-text searches because it mistakenly thinks 三 is a valid English word
As far as full-text searches: the problem is that inline Chinese in a lot of dictionaries isn't tagged as Chinese and so the system is still indexing it as English (or Italian or German or whatever). We should probably just add a little check for now to exclude anything containing Chinese characters from those other search profiles, but it's doing those full-text searches because it mistakenly thinks 三 is a valid English word