[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- <!--x-content-type: text/plain -->
- <!--x-date: Wed Jun 1 12:13:18 2005 -->
- <!--x-from-r13: genafnz ng irelfrpheryvahk.pbz (Pbo Fbkra) -->
- <!--x-message-id: [email protected] -->
- <!--x-reference: [email protected] -->
- <!--x-reference: 1117640088.9948.1.camel@localhost --> "http://www.w3.org/TR/html4/loose.dtd">
- <!--x-subject: [ale] OT: Using google search -->
- <li><em>date</em>: Wed Jun 1 12:13:18 2005</li>
- <li><em>from</em>: transam at verysecurelinux.com (Bob Toxen)</li>
- <li><em>in-reply-to</em>: <1117640088.9948.1.camel@localhost></li>
- <li><em>references</em>: <[email protected]> <1117640088.9948.1.camel@localhost></li>
- <li><em>subject</em>: [ale] OT: Using google search</li>
On Wed, Jun 01, 2005 at 11:34:47AM -0400, Jim Popovitch wrote:
> On Wed, 2005-05-25 at 21:47 -0400, Christopher Fowler wrote:
> > I'm having issues looking for exact phrases in google. I want to
> > look at for all the 'brower.toolbar' options for the Mozilla user prefs
> > file but I can not get Google to see the '.'. It keeps removing it and
> > breaking the words in too. Is there any way to tell google to look for
> > exactly what I ask for. I have this problem many times when I want to
> > find information about Perl modules. Google can ignore the '::'.
>
> >From Google:
>
> --------
> As you've noticed, Google doesn't recognize search terms containing
> periods, question marks, the @ sign, and other such characters. These
> characters are so common that including them in a search would greatly
> slow the delivery of the search results. Additionally, the use of
> punctuation on the web is so inconsistent (for example, there's no
> obvious way to decide between Mr. and Mr) that including it in the query
> often does more harm than good to the relevance of your search results.
>
> While we don't currently offer a way to force Google to recognize all
> special characters, we understand that many useful search terms do
> contain such characters. We've generated exceptions for terms like C++
> and $10, and we're studying ways to enable search terms like C/net.
> -------
>
> Interesting.
>
> -Jim P.
>
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> <a rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale">http://www.ale.org/mailman/listinfo/ale</a>
</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00037" href="msg00037.html">[ale] OT: Using google search</a></strong>
<ul><li><em>From:</em> james.sumners at gmail.com (James Sumners)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00025" href="msg00025.html">[ale] OT: Using google search</a></strong>
<ul><li><em>From:</em> jimpop at yahoo.com (Jim Popovitch)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00030.html">[ale] JavaScript Mouseover</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00032.html">[ale] OT: Good Support Company for 3Com IP Phone System?</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00027.html">[ale] OT: Using google search</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00037.html">[ale] OT: Using google search</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00031"><strong>Date</strong></a></li>
<li><a href="threads.html#00031"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>