9 PM
> To: Vladislav Safronov
> Cc: 'mod_perl list'
> Subject: RE: search engine for the Guide
>
>
> On Fri, 23 Jun 2000, Vladislav Safronov wrote:
>
> > Hi,
> >
> > Try http://www.comptek.ru/yandex/YandexFree.html
> > search engine for web
age-
> > From: Stas Bekman [mailto:[EMAIL PROTECTED]]
> > Sent: Thursday, May 04, 2000 2:10 PM
> > To: Matt Sergeant
> > Cc: mod_perl list
> > Subject: Re: search engine for the Guide
> >
> >
> > > On Thu, 4 May 2000, Stas Bekman wrote:
> &g
t
> Subject: Re: search engine for the Guide
>
>
> > On Thu, 4 May 2000, Stas Bekman wrote:
> >
> > > On Wed, 3 May 2000, Matt Sergeant wrote:
> > >
> > > > On Wed, 3 May 2000, Stas Bekman wrote:
> > > >
> > > > > Yeah,
On Fri, 19 May 2000, Randy Kobes wrote:
> On Fri, 19 May 2000, Stas Bekman wrote:
>
> > On Fri, 19 May 2000, raptor wrote:
> >
> > > hi,
> > >
> > > very interesting. Search for : "statinc" returns nothing and the box get filled
> > > with "tatinc" instead "statinc" ?!?!:")
> > >
> > > this u
On Fri, 19 May 2000, Stas Bekman wrote:
> On Fri, 19 May 2000, raptor wrote:
>
> > hi,
> >
> > very interesting. Search for : "statinc" returns nothing and the box get filled
> > with "tatinc" instead "statinc" ?!?!:")
> >
> > this under KDE viewer, now will try netscape ...!!
>
> it's not
On Fri, 19 May 2000, raptor wrote:
> hi,
>
> very interesting. Search for : "statinc" returns nothing and the box get filled
> with "tatinc" instead "statinc" ?!?!:")
>
> this under KDE viewer, now will try netscape ...!!
it's not the client -- it's a bug.
This happened after Randy has made
hi,
very interesting. Search for : "statinc" returns nothing and the box get filled
with "tatinc" instead "statinc" ?!?!:")
this under KDE viewer, now will try netscape ...!!
> > That would be nice to see. I'm afraid I'll continue on working on guide.
> > So if there anyone with a few free minutes on his hands, he/she might like
> > to contribute something back to community ;)
> >
> > Ideally, when we complete the tuning of the search engine, we will be able
> > to hav
>
> That would be nice to see. I'm afraid I'll continue on working on guide.
> So if there anyone with a few free minutes on his hands, he/she might like
> to contribute something back to community ;)
>
> Ideally, when we complete the tuning of the search engine, we will be able
> to have the whol
On Fri, 19 May 2000, Matt Sergeant wrote:
> On Thu, 18 May 2000, Randy Kobes wrote:
>
> > Another thing that was configured in is that words have
> > to be at least 3 characters long, which seems reasonable,
> > and also there's some stopwords that don't get indexed,
> > as they're too common. T
On Fri, 19 May 2000, Ged Haywood wrote:
> Hi all,
>
> On Thu, 18 May 2000, Randy Kobes wrote:
>
> > > The :: are stripped on the fly, since these cannot be used in index, so
> > > when you look for Foo::Bar you are actually looking for 'Foo && Bar'.
> >
> > That's a limitation of swish-e - you
On Thu, 18 May 2000, Randy Kobes wrote:
> On Fri, 19 May 2000, Stas Bekman wrote:
>
> > On Thu, 18 May 2000, Vivek Khera wrote:
> >
> > > looks good... one minor issue with the stickyness of the next search
> > > feature:
> > >
> > > type "lexical file handles" in your original search. the "e
On Thu, 18 May 2000, Randy Kobes wrote:
> Another thing that was configured in is that words have
> to be at least 3 characters long, which seems reasonable,
> and also there's some stopwords that don't get indexed,
> as they're too common. This list of stopwords is built
> by hand - so far it on
Hi all,
On Thu, 18 May 2000, Randy Kobes wrote:
> > The :: are stripped on the fly, since these cannot be used in index, so
> > when you look for Foo::Bar you are actually looking for 'Foo && Bar'.
>
> That's a limitation of swish-e - you can configure it to
> index characters like $, !, ... as
On Thu, 18 May 2000, Jeremy Howard wrote:
> Stas Bekman <[EMAIL PROTECTED]> wrote:
> > Ok, We have a preview ready for you. Randy Kobes worked hard to prepare
> > this one. So your comments are very welcome. If you like it we'll put this
> > into production.
> >
> > Please keep either the list
Stas Bekman <[EMAIL PROTECTED]> wrote:
> Ok, We have a preview ready for you. Randy Kobes worked hard to prepare
> this one. So your comments are very welcome. If you like it we'll put this
> into production.
>
> Please keep either the list CC'ed or if you reply to me in person, make
> sur
On Fri, 19 May 2000, Stas Bekman wrote:
> On Thu, 18 May 2000, Matt Sergeant wrote:
>
> > One more point... The indexer or the searcher (or both) has a broken
> > tokenizer for anything involving perl. Try searching for
> > Apache::Constants, for example.
>
> That's right. It's broken :( After
On Thu, 18 May 2000, Matt Sergeant wrote:
> Looks cool, except can we take the guide splitting back 1 level? It
> seems to be split on =head2's, and should be split (IMO) on =head1's.
The reason for splitting on any =head level lies in fact that there are
huge sections under =head1 which have m
On Fri, 19 May 2000, Stas Bekman wrote:
> Ok, We have a preview ready for you. Randy Kobes worked hard to prepare
> this one. So your comments are very welcome. If you like it we'll put this
> into production.
>
> Please keep either the list CC'ed or if you reply to me in person, make
> sure yo
On Fri, 19 May 2000, Stas Bekman wrote:
> Ok, We have a preview ready for you. Randy Kobes worked hard to prepare
> this one. So your comments are very welcome. If you like it we'll put this
> into production.
>
> Please keep either the list CC'ed or if you reply to me in person, make
> sure yo
Ok, We have a preview ready for you. Randy Kobes worked hard to prepare
this one. So your comments are very welcome. If you like it we'll put this
into production.
Please keep either the list CC'ed or if you reply to me in person, make
sure you keep Randy CC'ed -- all the kudos should go his way
Stas Bekman wrote:
> Yeah, it's a nice trick. The thing that defeats it a search engine, is
> it's freshness. We cannot tell google to rehash the Guide when there is a
> new version, and searching the outdated version is a bad idea.
Google is _very_ good at visiting frequently. Accounts for a
si
On Fri, 5 May 2000, Jeremy Howard wrote:
> At 01:28 PM 5/4/00 +0300, Stas Bekman wrote:
> >Two things:
> >
> >1) I'd better concentrate on improving the content and structure of the
> >Guide and will leave this search engine task to someone who needs to use
> >the Guide but find it unusable witho
On Thu, 4 May 2000, Gunther Birznieks wrote:
> I would think that apache.org would provide a free open source search
> engine as an infrastructural resource? Can't we take advantage of that? Or
> is perl.apache.org not actually part of apache.org infrastructure?
>
> It seems to me that a lot m
At 01:28 PM 5/4/00 +0300, Stas Bekman wrote:
>Two things:
>
>1) I'd better concentrate on improving the content and structure of the
>Guide and will leave this search engine task to someone who needs to use
>the Guide but find it unusable without the proper search engine.
>
>2) perl.apache.org doe
I would think that apache.org would provide a free open source search
engine as an infrastructural resource? Can't we take advantage of that? Or
is perl.apache.org not actually part of apache.org infrastructure?
It seems to me that a lot more apache.org sites would benefit rather than
perl.apa
On May 04, 2000 at 10:37:05 +0100, Matt Sergeant twiddled the keys to say:
> On Thu, 4 May 2000, Stas Bekman wrote:
>
> > On Wed, 3 May 2000, Matt Sergeant wrote:
> >
> > > On Wed, 3 May 2000, Stas Bekman wrote:
> > >
> > > > Yeah, I've been thinking about it. There was one site that has offere
On Thu, 4 May 2000, Stas Bekman wrote:
> On Wed, 3 May 2000, Matt Sergeant wrote:
>
> > On Wed, 3 May 2000, Stas Bekman wrote:
> >
> > > Yeah, I've been thinking about it. There was one site that has offered me
> > > to provide a good search engine and they did, but the problem is that they
> >
On Thu, 4 May 2000, Matt Sergeant wrote:
> On Thu, 4 May 2000, Stas Bekman wrote:
>
> > > Yes. On some of the search engines (AltaVista springs to mind) you can
> > > search for things on particular web sites, or even links to particular web
> > > sites. So as long as AltaVista keeps its search
> On Thu, 4 May 2000, Stas Bekman wrote:
>
> > On Wed, 3 May 2000, Matt Sergeant wrote:
> >
> > > On Wed, 3 May 2000, Stas Bekman wrote:
> > >
> > > > Yeah, I've been thinking about it. There was one site that has offered me
> > > > to provide a good search engine and they did, but the problem
On Thu, 4 May 2000, Stas Bekman wrote:
> > Yes. On some of the search engines (AltaVista springs to mind) you can
> > search for things on particular web sites, or even links to particular web
> > sites. So as long as AltaVista keeps its search contents up to date, you
> > can leverage their engi
On Wed, 3 May 2000, Matt Sergeant wrote:
> On Wed, 3 May 2000, Stas Bekman wrote:
>
> > Yeah, I've been thinking about it. There was one site that has offered me
> > to provide a good search engine and they did, but the problem is that they
> > didn't keep up with new releases, so people were se
On Wed, 3 May 2000, Stas Bekman wrote:
> Yeah, I've been thinking about it. There was one site that has offered me
> to provide a good search engine and they did, but the problem is that they
> didn't keep up with new releases, so people were searching the outdated
> version, which is quite bad -
liff rayman___ wrote:
> any thoughts on creating a search engine for the
> guide only?
>
> i am using htdig here and it seems to work real well.
Yeah, I've been thinking about it. There was one site that has offered me
to provide a good search engine and they did, but the pro
34 matches
Mail list logo
