IFilter is a Microsoft COM interface implemented by components that extract searchable content from a specific document format (Word, PDF, etc.) Lucene.NET does not use these components directly, they are used by whatever software you construct to populate the Lucene index with searchable content.
There is a lot of information on IFilter on Microsoft's site; and I think their optional use is beyond the scope of the Lucene.NET project. Would it help if I put together some simple examples of using Lucene.NET from VB ? - Neal -----Original Message----- From: Ed Jones [mailto:edmund.jo...@warc.com] Sent: Thursday, January 07, 2010 1:39 PM To: lucene-net-dev@lucene.apache.org Subject: RE: Question Remember that not everyone uses c#, many people use VB.net and although it's relatively simple to move it over to c#, moving from c# to Java is just one extra step where things can go wrong. At the time (3 years ago) I offered to spend time trying to make a set of examples such as how to use iFilters (I think that was the term) but nobody was interested so my attention moved elsewhere. -----Original Message----- From: Granroth, Neal V. [mailto:neal.granr...@thermofisher.com] Sent: 07 January 2010 19:37 To: lucene-net-dev@lucene.apache.org Subject: RE: Question I am very surprised by this comment. There is so much similarity between Java and C# that I found absolutely no difficulty with the discussion and examples in "Lucene in Action" and in directly applying the techniques to my C#/.NET projects. Maybe it would be helpful for some of those who find the java examples confusing to explain specifically why they are confusing. Then we might consider putting together some type of short "Guide to understanding Lucene for C# developers" or FAQ on the web site. - Neal -----Original Message----- From: Ed Jones [mailto:edmund.jo...@warc.com] Sent: Thursday, January 07, 2010 3:57 AM To: lucene-net-dev@lucene.apache.org Subject: RE: Question All I can say is that we found the lack of examples for .net problematic as when you are not too up to speed with Java there are a lot of basic hurdlers to overcome. -----Original Message----- From: Olivier Spinelli [mailto:olivier.spine...@invenietis.fr] Sent: 07 January 2010 09:55 To: lucene-net-dev@lucene.apache.org Subject: RE: Question <quote> Lucene.Net sticks to the APIs and classes used in the original Java implementation of Lucene. The API names as well as class names are preserved with the intention of giving Lucene.Net the look and feel of the C# language and the .NET Framework. For example, the method Hits.length() in the Java implementation now reads Hits.Length() in the C# port. In addition to the APIs and classes port to C#, the algorithm of Java Lucene is ported to C# Lucene. This means an index created with Java Lucene is back-and-forth compatible with the C# Lucene; both at reading, writing and updating. In fact a Lucene index can be concurrently searched and updated using Java Lucene and C# Lucene processes. </quote> It's merely all about switching from camelCase to PascalCase... HTH Spi -----Message d'origine----- De : Ed Jones [mailto:edmund.jo...@warc.com] Envoyé : jeudi 7 janvier 2010 10:27 À : lucene-net-dev@lucene.apache.org Objet : RE: Question My problem with Lucene in Action and all the examples on the internet is that they were all in Java and you have to understand exactly what Java is doing to understand it all properly. It's for this very reason we had to shun using Lucene.net in major projects. I wanted dearly to use it but the learning curve was far too steep and there appears to be very very few .net examples of code or help. Instead we have invested a significant amount of money in buying in a much more commercial search engine. I am keeping an eye on the Lucene.net project though in-case it can be used in other parts of our business, but again the same will apply, we will need more non Java examples. Ed -----Original Message----- From: Roger Chapman [mailto:ro...@stormid.com] Sent: 07 January 2010 09:21 To: lucene-net-dev@lucene.apache.org Subject: RE: Question >From what I can remember the book Lucene in Action has a good section on indexing documents and PDFs http://www.manning.com/hatcher2/ Roger. -----Original Message----- From: Ben Martz [mailto:benma...@gmail.com] Sent: 06 January 2010 19:51 To: lucene-net-dev@lucene.apache.org Cc: <lucene-net-dev@lucene.apache.org> Subject: Re: Question Todd, I would definitely take Michael's advice to learn more about the overall issue before you get too far. A quick answer that may help is Windows does not ship with an iFilter for PDF built-in. Installing Adobe Reader 8 or higher will install a decent PDF iFilter. I am a little surprised by your question though - I assume that you have access to your own source code and could examine the result from the iFilter that's being fed to the IndexWriter and compare the behavior in the TXT case with the behavior in the PDF case? Cheers, Ben Sent from my iPhone On Jan 6, 2010, at 10:13, Michael Garski <mgar...@myspace-inc.com> wrote: > Todd, > > You'll need some way to extract the text from the PDF prior to > indexing. I'm not familiar with any packages that can do that but I > have heard of them. You may want to try searching the mailing list > to see if there has been mention of one previously. Lucid > Imagination hosts a great mailing list search tool at http://www.lucidimagination.com/search/ > > Michael > > -----Original Message----- > From: Todd McIndoo [mailto:tmcin...@speedyscan.biz] > Sent: Wednesday, January 06, 2010 10:11 AM > To: lucene-net-dev@lucene.apache.org > Subject: Question > > Sorry if this is duplicate > > > > We are using Lucene.net of version 2.0.0.4. I am trying to search a > document > which contains lots of PDFs. I want to search a document, which > contains a > specific word, using Lucene.net. We are yielding results in text > documents > but not in PDF. Is there something we have to do to be able to > search in PDF > > Documents. All ifilters have been installed on the computer so I do > not > think that is the issue. > > > > Regards, > > SPEEDY SOLUTIONS > > > > Todd McIndoo >
