Difference between revisions of "Complete Lexicon Functionality"
From CrossWire Bible Society
(→Potential Lexicon Functionality) |
|||
| Line 10: | Line 10: | ||
*The user should be able to search the text of dictionary entries. | *The user should be able to search the text of dictionary entries. | ||
| − | =Solutions related to module creation= | + | ==Solutions related to module creation== |
| − | =Solutions related to the engine= | + | ==Solutions related to the engine== |
| − | =Solutions related to front-ends= | + | ==Solutions related to front-ends== |
Revision as of 02:24, 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.
What Complete Lexicon Functionality Looks Like
- A complete lexicon should be able to have front-matter (preface, introduction, bibliographic information, tables of abbreviations, etc.).
- Quick lookup from a Bible module should be easily accessible by hovering over, right clicking over, or double clicking on a word.
- Users should be able to browse a lexicon by letter using a tree structure.
- The print order of entries should be preserved to ensure that quick lookup is accurate.
- The user should be able to search the text of dictionary entries.
