Please support partial-match search function like 1Password 7

I don't think that article is relevant. Windows Search uses a full-text method similar to 1Password's, and what is being requested from 1Password is an improved partial-text matching ability. Windows has a complicated relationship with UTF and internal represenation of text, and the text-file-with-BOM weirdness is largely limited to Windows itself.

But it does point out that Search Is Hard, and Text Character Encoding Is Hard. :-)

This is fun:
https://jeremyhussell.blogspot.com/2017/11/falsehoods-programmers-believe-about.html

1P_Ben @"ali.hazime"
Thanks for replying. I saw an article similar to this one.

Windows Search does not have the ability to do a full-text search of UTF-8 text
https://ascii-jp.translate.goog/elem/000/004/058/4058837/?_x_tr_hl=ja&_x_tr_pto=wapp&_x_tr_sl=ja&_x_tr_tl=en

I hope this gives you some insight.

viswiz

Reverting to the way 1Password 7 worked isn't in the cards. We'll continue to evaluate how we can move search forward, but I can say with some certainty if the line in the sand for you is having it work exactly as it did in v7 then that isn't where we're headed.

Ben

@"ali.hazime" you are working on this problem since the first early access version of 1PW8... sadly without any visible progress. I'm really loosing patience and confidence in AgileBits. Substring search is an essential and widely accepted search feature. 1PW8 finds only a fraction of what all previous versions were able to find. Even worse it doesn't even show directly what it has found. It's using a filtered overlay window instead of just showing all results inline. One has to use CMD+Enter to see all results. You've added Filter/Find as a secondary search approach that works much better but that is still not on par with 1PW7. My workflow is now: using Find/Filter first, using Search second, giving up and returning to 1PW7.
Please bring back th 1PW7 search inlcuding its UI and algorithm... at least as an option.

ticksgt yes, this is also a significant issue in English and other languages. You gave perfect examples.

I’d like to learn about the lack of word separation and additional impact for Japanese.

I find the technical explanation for the change in behavior to be interesting but unsatisfying. It’s a distraction - storing strings as UTF8 doesn’t prevent partial marching, the choice of search engine does.

Hey ticksgt, thanks for reaching out.

I certainly understand where you're coming from as searching in 1Password 8 doesn't work the same way it did in 1Password 7. There are some technical reasons for this, as one of our developers, Rob, explains here:

https://1password.community/discussion/comment/635627/#Comment_635627

With that said, we are still working on making search work well for everyone and have an internal issue raised for this. We greatly appreciate you sharing your use case and I'll be sure to add your comments to the internal issue.

Ali

IDEA-I-527