The different Greasemonkey scripts also do a good job finding some implementations of microformats:<br><br><a href="http://microformats.org/wiki/greasemonkey">http://microformats.org/wiki/greasemonkey</a><br><br>Cheers!<br>
<br>Pat<br><br><div><span class="gmail_quote">On 3/24/06, <b class="gmail_sendername">Dimitri Glazkov</b> <<a href="mailto:dimitri.glazkov@gmail.com">dimitri.glazkov@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
This has been an on-and-off discussion that ought to be documented<br>somewhere -- well, at least its progress. I wouldn't say that there's<br>a total agreement on how it should be done, but here's my opinionated<br>take:
<br><br>If you know what you're looking for, you'll find it. If you don't know<br>what you're looking for, why are you looking for it?<br><br>Look at Tails (<a href="http://blog.codeeg.com/tails-firefox-extension">http://blog.codeeg.com/tails-firefox-extension
</a>) -- it<br>finds everything it understands, and nothing else. It won't find<br>hAtom, because it doesn't understand it. And it's perfectly fine -- if<br>you don't hAtom, I don't want you to be looking for it.<br><br>:DG
</blockquote></div><br clear="all"><br>-- <br>Pat Ramsey<br><a href="mailto:ramsey.pat@gmail.com">ramsey.pat@gmail.com</a><br><a href="http://www.southwestern.edu/~ramseyp">http://www.southwestern.edu/~ramseyp</a>