| From: | Robert Bernier <robert(dot)bernier5(at)sympatico(dot)ca> |
|---|---|
| To: | pgsql-www(at)postgresql(dot)org |
| Subject: | Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard |
| Date: | 2006-08-02 17:57:28 |
| Message-ID: | 200608021357.28738.robert.bernier5@sympatico.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Wednesday 02 August 2006 13:33, Robert Treat wrote:
> > ASPSeek can as well (they're called stopwords) but it won't help in this
> > case because even if we don't ignore IN et al. it'll still match
> > virtually every page.
>
> What would be nice would be to have a first level of human specified
> keywords that return specific information, above and beyond the general
> search. This could operate similarly to rtfm_please on irc or my rtfmbot
> on AIM. This way when someone searches on something like IN, we can say
> "you're probably looking for this --> link" If there are general search
> results, we could show them after the pre-spelected links.
Could a set of links be returned, somewhere on the page, that would always
refer to one or more keywords when a single word is used as the search
criteria?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2006-08-02 19:12:44 | Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard |
| Previous Message | Robert Treat | 2006-08-02 17:33:22 | Re: [Fwd: [BUGS] BUG #2560: Web page documentation hard |