As you may know, KDE4 will use Strigi for meta information extraction instead of the old KFilePlugin classes.
Since Strigi’s analyzer work in a different way, lot of code has to be ported. Unfortunately, after a good start, some relevant analyzers were still missing.
But in the last weeks Strigi gained support of:
- wave file
- avi files
- txt files
- dds files
- rgb files
- sid files
- ico files
I’ve also updated this summary page. As you can see there’s still some work to do, but don’t worry… I’ll try to do the best 
Entries (RSS)
Great work Flavio.
I’ll check them out soon so we can do a new release quickly.
I’m glad the Strigi team plodded on while I was offline.
Hi! I mostly use strigi to index fortran 90 code and photos. It seems that fortran and specially the newer standards f90 f95 and 2003 are not very visible in the kde world. Where should I start in order to be able to write/help writing and testing a fortran strigi analyzer?
Cheers and keep up with the good work!
First of all you should read this good tutorial.
Then I suggest you to look at CppLineAnalyzer, I think you can use it as starting point.
I am looking forward to trying it out in KDE4.0
Is there any plan to get an analyzer for LyX? Most of my documents are in this format and strigi would be much more useful for me…
Anyways happy KDE4.
I’ve looked at Lyx files, they’re plain tex files (as far I have seen, tell me if I’m wrong).
So it won’t be hard to support them.
+1 entry in my TODO list
Thats excellent news.
However I am afraid that LyX and TeX differ a bit… LyX-file format is in a way based on TeX, but is more verbose.
But I do not know if this matters for strigi :).
example in LyX:
\begin_layout Title
Title_example.
\end_layout
In (La)TeX:
\title{Title example. }
etc.
If you want I could email you some LyX and corresponding TeX files ?
You’re right, they’re a bit different.
Don’t worry, I’ll look at examples shipped with Debian packages
Ciao Flavio, why don’t you move to TechBase for the wiki?!
good news to hear about multimedia files additions for strigi, I’m going to check the code right now!
It’s just a temporary page made for job organization.
When all KFilePlugins will be ported to Strigi analyzers I think it will be forgot…
Is Dolphin or Konqueror aware of strigi analyzers meta information?
It is strigidaemon necessary to extract meta information?
I currently have some strigidaemon process runing but I don’t know how to get the meta file information extracted with strigi analyzers, I tried with strigiclient but it doesn’t worked for me.
Thanks for your work.
Sorry, I saw your comment just today.
Actually (with KDE 4.0.0) meta informations extracted by Strigi analyzers are not yet used by KDE.
The situation will change with KDE 4.1.0, when a better Strigi interface will be released and adopted by KDE developers.