Registered Member
|
How do you recognize errors in xmlindexer and rdfindexer? I don't see any obvious one. In the file I uploaded in the bug page, I don't see any text when I run xmlindexer or rdfindexer (so that's an indication). In mln-manual.pdf, everything looks fine though but still impossible to index it. Something else... I don't have many strigi packages installed (like strigi-daemon) in my system but I guess I don't need them as well... Even the package strigi-utils providing xmlindexer and rdfindexer, I had to manually install it. Here is a list of packages and their corresponding versions in my system returned after a search for strigi.
|
Registered Member
|
When there is output there is no obvious method but you can compare results between an indexed pdf and a not indexed a pdf and try to detect what is happening. To complicate more this stuff indexer could be working but adding the resource to Nepomuk could fail but, at least, you can confirm that there is not a problem at indexer level.
Of course, if there is no text then indexer is failing. In my system, and with my debug level, I obtained and "Error in parsing" msg indexing your pdf. As I explained, when I repaired the pdf indexer using pdftk there is no error parsing the file so seems like this pdf has some type of damage. As both fixed and not fixed pdfs are indexed in my system I can't confirm if a repaired pdf will be indexed in your system. Finally about your installed versions I can't help you because I don't use Ubunto, maybe others could help you. I can only confirm you that in openSUSE 11.3 the pdf is indexed.
Ignacio Serantes, proud to be a member of KDE forums since 2008-Nov.
|
Registered users: bancha, Bing [Bot], Google [Bot], Sogou [Bot]