On Mon March 27 2006 14:36, Joe Shaw wrote: > Hi, > > On Sun, 2006-03-26 at 22:04 -0500, afaiq aol com wrote: > > However, none of the .doc MS Word files do not get indexed. When I > > 'touch' a word file, I see the following message in the > > current-IndexHelper log > > 060326 2135548346 26359 IndexH DEBUG: > > +file:///home/afaiq/Documents/test.doc > > 060326 2135548350 26359 IndexH DEBUG: No filter for > > /home/afaiq/Documents/test.doc (application/msword) > > You can simulate this by running the "beagle-extract-content" tool in > the tree. That way you don't need to run the daemon to debug it. > > > Any ideas why? > > My guess is that the library isn't being found for some reason. Run > beagle-extract-content with the MONO_LOG_LEVEL=debug MONO_LOG_MASK=dll > environment variables and see if you see any errors. Likely something > about unresolved symbols, or not being able to find a certain library. > This is pretty common when you build libraries from source. You may > need to set the LD_LIBRARY_PATH to point to the location where you > installed wv. I'm having the same problem with Word files. I haven't built anything from source. I installed the latest Debian packages from Debian Sid. Beagle is working wonderfully except for not indexing the contents of Word files. I have several wv Debian packages installed including: wv (which is version 1.2.1-1), libwv- 1.2.1, libwv2-1c2 and libwv2-dev. The library files, libwv-1.2.so.1.0.0 & libwv-1.2.so.1 are in /usr/lib. Rick -- Rick's Law: What cannot be imagined will be accomplished by a fool.
Attachment:
pgpUwP0Nx6bfJ.pgp
Description: PGP signature