>Hi,
>
>>
>>As for the special characters, this is a limitation on the search engine. Since the last two months, we are much better than we we had for years but I just do not have the infrastructure to support what it would take for those special characters to be included and used for the search.
>>
>If the search engine is unable to look for a phase containing operators like "+&" and so on, that I can still understand, for example some of the operators might be used by the search engine itself to form a more complicated search patern...
>But how could chars like underscore "_" become a problem? If you are enhancing UT, why not make the search engine better first?
>
>If my memory serves me right, I can search for "_screen" in UT forum without problem in the past... Can anyone confirm this?
>
>I Google for "_Screen", in just 0.2 seconds, it produce me 996,000 findings, well you know what happen when I try the samething in this forum. Google is for general use and search engine here is for programmers, it is very sacarstic that the former does it better to look for coding syntax like _screen. (even more ironic is the latter refuse to search for technical term)
>I hope you take it seriously, at least make it able to search phase containing general code syntax like "_object.method name"
>
>Your poor search engine only result in 1 thing, a search for "something" almost always end up as new topic asking for help... That means the same question about that "something" and same answers (if any from the group) will keep repeating... Isn't this a big issue for you?

Well, that's actually a real advantage, isn't it? It keeps the community further alive! :)

But to be honest, you made good observations. Even the new search engine is not state of the art, that's a fact, although Michel doesn't like that being said here, for obvious reasons. And I understand he's having another priority right now. That priority is a real number one. But a better search engine should be number two, IMO.