Summary: | kpdf and kate/kwrite seamless integration with advanced search engines (strigi, tenor) | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Matteo Azzali <matte.az> |
Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | wishlist | CC: | cullmann, jos |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Matteo Azzali
2006-11-21 02:01:46 UTC
whops, *insert hydroelectric and go to desired part. sorry Kate supports --line <line> and --column <column> paramters to navigate to a location inside a document. I do not know if strigi has that information? I don't think so, it just collects all the words of a document. Also it's supposed to get only first occurence of every word (for database space size....)in a document, so it would be really better to have the search dialog open and already "filled" (like what happens when you select a word and then hit ctrl+f .....) Strigi does not know the line number of text files form the index. The GUI that you use for searching could look for the line number and start kate at the right position. However, since nearly every app has a search function, allowing a command-line parameter which passes the search terms is more versatile. You could run: okular --highlight 'kde' --highlight 'release' myfile.pdf On the search GUI side, we'd need a configuration file which knows about the various attributes that are supported by the different apps. Cheers, Jos As KDE uses now completly other stuff for search, this is out of date ;) |