On Thu, Mar 05, 2009 at 11:08:33AM +0100, Christian Boos wrote: > > W. Martin Borgert wrote: > > On 2009-03-04 18:06, Chris Mulligan wrote: > > > >> This is motivated entirely by a local need. As our primary internal tracs > >> grow (thousands of tickets and wiki pages) it's becoming harder and harder > >> for users to find already existing content. They end up making lots of > >> dupes, making the problem even worse the next time. > >> > > > > Yes, the trac search facilities are good, but sometimes not good > > enough. Sometimes one likes to search "the whole thing", e.g. > > including PDFs in the SVN trunk etc. I'm not sure, if whoosh > > addresses this problem. > > > > Searching content in the repository is addressed by the RepoSearch > plugin on trac-hacks, if I'm right. > > http://trac-hacks.org/wiki/RepoSearchPlugin > > Looking for content inside non-text file like a .pdf would require an > additional extraction/analyze step.
Perhaps an infrastructure could be built such that filters could be applied to mimetypes and the search is performed on the results of that filter. For example, you could apply pdftotext as a filter for pdfs and search the resulting text or you or antiword to (horrible) .doc files. > Also, I don't know if the plugin allows for searching the path names, > useful for locating some source file you have no idea in which > subproject or branch it is ;-) > > -- Christian > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
