(I've re-ordered this message to reply to it). On Fri, 8 Mar 2002, d.brodale wrote: > > (1) Links [http://links.sourceforge.net/] doesn't appear > to be a 'recognized' browser. > > (3) Is there documentation somewhere describing what, in > fact, qualifies as "Netscape (compatible)" in the Browser > Summary Report? Or a human-readable list of User Agents > known to Analog?
There are no recognised browsers. No, that's not true. There are no _unrecognised_ browsers. Some very popular browsers that pretend to be "Mozilla (compatible)" have special cases to pull out their real names (see tree.c:764). Apart from these, anything that pretends to be "Mozilla (compatible)" is listed as that. If it gives its real name, that's listed in the report, even if it's not known to analog before. > I added the following directive to the included config > file: > > BROWSUMEXCLUDE REGEXP:^Mozilla$ > > Now, I would think that this would simply exclude > from the Browser Summary Report only User Agent > strings wholly matching "Mozilla". That's how the > expression works for the Operating System Report > with the ROBOTINCLUDE directive. However, using > the above BROWSUMEXCLUDE directive removes *all* > instances of Mozilla [as in, www.mozilla.org] from > the Browser Summary Report. > > Is this a subtle bug, or am I supposed to see two > differing interpretations of the same regular > expression for these two cases? It's not a bug, it's the correct behaviour. BROWSUMEXCLUDE doesn't remove browsers. It removes _lines from the Browser Summary_. In this case it removes the line "Mozilla" (and therefore everything below it in the hierarchy). > (a) Is there an easy way to apply a BROWSUMEXCLUDE > directive for each ROBOTINCLUDE directive supplied? > As I think I understand it, should I want to keep > defined robots from appearing in the Browser Summary, > I have to supply a matching BROWSUMEXCLUDE directive > for each and ever ROBOTINCLUDE directive. This doesn't > seem correct or workable over large data sets. No, there is no easier way. And my previous comment shows why this probably isn't what you want to do anyway. Now, there is a case for allowing "BROWEXCLUDE robots", but it would mean making a special case of browsers in the exclusion code, and I really don't want to do this. I don't see the current solution as unscalable as long as your text editor can do both cut-and-paste and search-and-replace. :-) -- Stephen Turner, Cambridge, UK http://homepage.ntlworld.com/adelie/stephen/ "This is Henman's 8th Wimbledon, and he's only lost 7 matches." BBC, 2/Jul/01 +------------------------------------------------------------------------ | This is the analog-help mailing list. To unsubscribe from this | mailing list, go to | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | List archives are available at | http://www.mail-archive.com/[email protected]/ | http://lists.isite.net/listgate/analog-help/archives/ | http://www.tallylist.com/archives/index.cfm/mlist.7 +------------------------------------------------------------------------
