Difference between revisions of "Complete Lexicon Functionality"
From CrossWire Bible Society
m (moved Lexicon Funcionality to Complete Lexicon Functionality: Misspelled title, makes it more clear) |
|||
| Line 1: | Line 1: | ||
| + | =Issues with the Current Lexdict Module Driver= | ||
| + | *It handles basic glossaries in non-accented Latin scripts as well as standard Strong's modules quite well. However, the module is created with an index that is ordered by bytes, and this reorders dictionaries in some languages in a way that is undesireable. | ||
| + | *It does not allow for front-matter or for searching entry text or browsing in a tree structure. | ||
| + | *Only one type of key is supported for each module. For TEI modules, using <nowiki>n="<key1>|<key2>"</nowiki> simply results in the two keys being merged together. | ||
=Potential Lexicon Functionality= | =Potential Lexicon Functionality= | ||
=Issues/Ideas related to module creation= | =Issues/Ideas related to module creation= | ||
=Issues/Ideas related to the engine= | =Issues/Ideas related to the engine= | ||
=Issues/Ideas related to front-ends= | =Issues/Ideas related to front-ends= | ||
Revision as of 02:16, 20 March 2009
Contents
Issues with the Current Lexdict Module Driver
- It handles basic glossaries in non-accented Latin scripts as well as standard Strong's modules quite well. However, the module is created with an index that is ordered by bytes, and this reorders dictionaries in some languages in a way that is undesireable.
- It does not allow for front-matter or for searching entry text or browsing in a tree structure.
- Only one type of key is supported for each module. For TEI modules, using n="<key1>|<key2>" simply results in the two keys being merged together.
