home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ukma!wupost!cs.utexas.edu!bcm!lib!oac2.hsc.uth.tmc.edu!user
- From: cshotton@oac.hsc.uth.tmc.edu (Chuck Shotton)
- Newsgroups: comp.infosystems.gopher
- Subject: Gopher's built-in WAIS search bug?
- Message-ID: <cshotton-161192152019@oac2.hsc.uth.tmc.edu>
- Date: 16 Nov 1992 21:27:12 GMT
- Sender: usenet@lib.tmc.edu
- Followup-To: comp.infosystems.gopher
- Organization: Academic Computing
- Lines: 51
- Nntp-Posting-Host: oac2.hsc.uth.tmc.edu
-
- I've run across a problem using gopher's built-in support for
- "understanding" WAIS .src files. We have several WAIS sources available
- through gopher. Until recently, access to these sources was through the old
- Gopher->WAIS gateway. When gopher 1.03 came along with built-in WAIS
- support for .src files in a gopher dir, we switched over.
-
- It now appears that gopherd really munges the data when it returns it to
- the gopher client. Titles of entries in a WAIS source which used to be
- simple one or 2 word titles (on the first line of a document indexed as
- "para") now consist of all the text in a particular WAIS search result
- that'll fit on one line in the gopher client's list.
-
- For example, a WAIS query that would normally return the following info
- (using the gopher->WAIS gateway):
-
- Index word(s) to search for: SPAM
-
- 1. SPAM - A meat product
-
- <select 1>
-
- SPAM - A meat product
- SPAM is one of the modern wonders of the world.
- It comes in two colors.....
-
- gopherd 1.03 returns the same info in the following form:
-
- Index word(s) to search for: SPAM
-
- 1. SPAM - A meat product SPAM is one of the modern wonders of the world. It
- com
-
- <select 1>
-
- SPAM - A meat product SPAM is one of the modern wonders of the world. It
- comes in two colors.....
-
- In other words, it appears as if all carraige control info is totally
- ignored. When the same data is accessed via the old WAIS gateway, all
- clients seem to work just fine but every widely available client chokes
- when the built-in .src support of gopherd is used.
-
- This must be a known "feature" of gopherd 1.03's support for .src files. Is
- there a work-around or patch to fix the problem?
-
- --_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
- Chuck Shotton |
- Ass't Director, Academic Computing | "This space for rent."
- UT Health Science Center Houston |
- cshotton@oac.hsc.uth.tmc.edu |
- _-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
-