[sword-devel] module modtime -vs- CLucene index out-of-date-ness

[DM Smith]

Karl Kleinpaste wrote:
> Chris Little <chrislit at crosswire.org> writes:
>   
>> compression takes 5 minutes for a single Bible (OT+NT) on my Win32 
>> system (2GHz Pent-M, 7200RPM drive), due to the constant disk access.
>>     
>
> I had similar thoughts.  I've just installed WinSword + Sword libs +
> GnomeSword on my wife's 1.8GHz dual-core WinXP laptop and now I'm
> indexing 248 modules.  It's been running for ~4 hours and has quite a
> way to go.
>
> BTW, would someone please update mkfastmod so that it outputs a final
> '\n'?  I would appreciate it.
>
> I also just discovered that BibleTime creates its own CLucene indices,
> rather than using those created by mkfastmod under $DataPath/lucene.
> /mutter/ /mumble/  No wonder BT has been bugging me about "some
> modules need to be indexed before they can be searched" even though I
> have everything already indexed on my own machines.

JSword also creates its own indexes and places them in a different 
location than Sword. But for now that is goodness, we use different 
analyzers to create the indexes. And also, Sword indexes Strong's 
numbers, which JSword does not do. To further complicate the matter we 
are using Lucene 2.1, which creates indexes that Sword cannot read. 
CLucene just can't keep up with Lucene:)

However, JSword can use the Sword indexes with little problem.