tag:blogger.com,1999:blog-18974949.post8038014092132856772..comments2024-03-23T01:15:42.294-06:00Comments on Open Source and Enterprise Architecture: Google Desktop for Linux vs. BeagleAndrig T Millerhttp://www.blogger.com/profile/05386153547711039401noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-18974949.post-90994001108082492562007-07-03T13:39:00.000-06:002007-07-03T13:39:00.000-06:00Also, looking at the file sizes, I greatly suspect...Also, looking at the file sizes, I greatly suspect that you are hitting a bug in Beagle. For a 20 gig home directory, 11 gigs in ~/.beagle is too big. It should be around 10% the size, so I would expect something in the 1-2 gig region.<BR/><BR/>Again, feel free to email me and we can try to work it out if you're interested. :)<BR/><BR/>JoeUnknownhttps://www.blogger.com/profile/05480659835226012192noreply@blogger.comtag:blogger.com,1999:blog-18974949.post-26795165723365866512007-07-03T13:37:00.000-06:002007-07-03T13:37:00.000-06:00With Beagle, I have been frustrated at times that ...<I>With Beagle, I have been frustrated at times that it couldn't find files that I knew were there, but couldn't remember where I had saved them. Isn't that what desktop search is all about? In fact, as a result of trying to find a Portable Document Format (PDF) document that I had saved from the web, I opened a Bugzilla case thinking that Beagle was not indexing PDF's. It turned out that Beagle was indexing the PDF's, but Beagle only indexes based on a files metadata, not its entire contents. That explains why it couldn't find the file I was looking for, because the search phrase I was using didn't match the files metadata, but part of its content. So, I had the perfect test case to see whether Google Desktop could find what Beagle couldn't.</I><BR/><BR/>Can you reference the Beagle bug for this? Because it's not quite right; both Beagle and GDL use the same tools (pdftotext) to extract text from PDF files and index them.<BR/><BR/>If you're having issues indexing with Beagle, please email me and I'll try to help you track it down.<BR/><BR/>Joe Shaw<BR/>joe@ximian.comUnknownhttps://www.blogger.com/profile/05480659835226012192noreply@blogger.com