??? 11/28/07 09:50 Read: times |
#147491 - Common problem Responding to: ???'s previous message |
Craig Steiner said:
In the case of your example, searching for "K&R" is actually going to search for messages with the letter "K" and "R" in it. The ampersand is treated as a delimiter as if it were a space, and is ignored. Aha - I thought so: http://www.8052.com/forumchat/read.phtml?id=147389 Richard Erlacher said:
Yes, it's a problem that people can enter a text string that, later, can't be searched-for because it contains what turns out to be a delimiter ... I imagine this is a problem with many searches. I'd think something like quotes might serve in that capacity. Yes, AltaVista has this "problem" - it treats things like dots and hyphes as wildcards even in a quoted string; for example, searching for "J.P. Smith" would treat those dots as wildcards, rather than looking for Mr Smith's initials in that particular format Dunno if Google is similar... |
Topic | Author | Date |
about that SEARCH feature | 01/01/70 00:00 | |
it's the choice of the proper keywords | 01/01/70 00:00 | |
ampersand | 01/01/70 00:00 | |
No | 01/01/70 00:00 | |
Maybe, but if they tried it last time ... | 01/01/70 00:00 | |
Search facility | 01/01/70 00:00 | |
maybe it's the other way around | 01/01/70 00:00 | |
Common problem | 01/01/70 00:00 | |
a q'n'd fix suggestion... | 01/01/70 00:00 | |
How is the search string interpreted? | 01/01/70 00:00 | |
a few things found out by experimenting... | 01/01/70 00:00 | |
You\'re right | 01/01/70 00:00 | |
There may be more to this than meets the eye! | 01/01/70 00:00 | |
Use quotes to search for a phrase | 01/01/70 00:00 | |
made it a FAQ | 01/01/70 00:00 | |
Google, temporarily | 01/01/70 00:00 | |
That should work ... but ... | 01/01/70 00:00 | |
TTL Compatibility | 01/01/70 00:00 | |
There are two separate issues | 01/01/70 00:00 |