There are a few things being mixed up here:
Module driver type: RawLD, zLD, etc., specified in the module's .conf
ModDrv entry.
Source text MARKUP: OSIS, TEI, ThML, specified with the SourceType entry.
Import format: OSIS, 'Imp', VPL, etc. this only dictates which import
utility is necessary to use when creating the module.
A TEI LocalOptionFilter to put TEI fields into EntryAttributes would
allow any TEI field to be searching on with SWORD. We just need a rich
modules to prompt the need to create such.
We've discussed allowing the CLucene indexes to be created on any
EntryAttributes field, so the next step would be to determine if
indexing these fields would be worth the effort. My guess is that you
would be <2 second response from an unindexed search right now.
Hope this helps.
Troy
On 08/25/2013 08:26 AM, Timothy S. Nelson wrote:
On Sat, 24 Aug 2013, ref...@gmx.net wrote:
Lexica in sword are not build with OSIS.
Ah, I think I see. Are you referring to the fact that they have
to be converted to IMP files first?
Thanks,
---------------------------------------------------------------------
| Name: Tim Nelson | Because the Creator is, |
| E-mail: wayl...@wayland.id.au | I am |
---------------------------------------------------------------------
----BEGIN GEEK CODE BLOCK----
Version 3.12
GCS d+++ s+: a- C++$ U+++$ P+++$ L+++ E- W+ N+ w--- V- PE(+) Y+>++
PGP->+++ R(+) !tv b++ DI++++ D G+ e++>++++ h! y-
-----END GEEK CODE BLOCK-----
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
