declan@remus.rutgers.edu (Declan McCullagh/LZ) (02/04/91)
In article <1991Feb3.172701.26600@sjuphil.uucp>, dcarpent@sjuphil.uucp (D. Carpenter) writes: > The one problem that I _have_ had is with Framemaker and the > Digital Librarian. The DL doesn't recognize Frame files, i.e, > won't index them. Someone (Christopher ? Sorry, I deleted the > file) wrote to say that the file frame-ascii in /uslib/indexing > was a symbolic link to a file that no longer exists, and that it > needed to be changed to point to the new frame-ascii that comes > with Frame 2.0d. I tried this but still couldn't get it to work. > I've since talked to people at Frame and at NeXT and no one is > yet sure what is wrong, although the person at NeXT told me that > it was "a known problem" and that he would research it further. After I created a link from /usr/lib/indexing/frame-ascii to /LocalApps/FrameMaker.app/frame-ascii, DL seemed to have no problem indexing and searching my (relatively short) FrameMaker documents. Perhaps if you look at the Console messages, you can track down the problem. Strangely enough, DL didn't seem to be able to search for words in unindexed FrameMaker documents. When a word was entered and the "Search" button clicked, DL would scan through the Frame documents and inform me that the word was present in each of the documents (even when it wasn't). Indexing the directory fixed this. Declan McCullagh Independent NeXT Developer