Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!samsung!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!agate!shelby!SUMEX-AIM.STANFORD.EDU!lane From: lane@SUMEX-AIM.STANFORD.EDU (Christopher Lane) Newsgroups: comp.sys.next Subject: re: DigLibrary and Frame Message-ID: Date: 31 Jan 91 16:17:38 GMT References: <1991Jan30.154647.10832@sjuphil.uucp> Sender: Christopher Lane Organization: Internet-USENET Gateway at Stanford University Lines: 26 In <1991Jan30.154647.10832@sjuphil.uucp>, David Carpenter writes: >When I re-index things that I have on-line, the Digital Librarian >ignores Framemaker files! >... >(By the way, I'm using the 2.0d version of Framemaker that was made >available at the last minute for those upgrading to 2.0. I don't see >how this would cause the problem, however. I went through and re-saved >several files to see if this would make DL recognized them, but it had >no effect) The problem I found is that /usr/lib/indexing/frame-ascii is a symbolic link to FrameToAscii which doesn't exist in (NeXT) 2.0. I've seen messages about copying this file from the 1.0 release but the release of FrameMaker 2.0d we received had this file under FrameMaker.app/frame-ascii. So to solve the problem, I did: >cd /usr/lib/indexing >rm frame-ascii >ln -s /LocalApps/FrameMaker.app/frame-ascii If you don't have FrameMaker.app/frame-ascii, then you'll have to grab FrameToAscii from 1.0 and just place it in /usr/lib/indexing. - Christopher -------