Morph Search
Morph searches are no longer constrained by a single morphology. Previously, the resources that would be searched in were only those that supported the selected morphology. The workflow has now changed. Rather than select a morphology, select the resources and references to search in. These constrain the available morphologies to select from, which are now presented in the morph picker control (the popup that appears after typing “@”.)
If more than one morphology is available in the selected resources and references, lemmas, roots, and morph references may be ambiguous to the search parser. In these cases the autocompleter will use the explicit data type reference syntax, e.g. <Lemma = lbs/el/λόγος> for lemma:λόγος, <LogosMorphGr ~ V???????> for @V. The simpler syntax will be used where possible, e.g. when searching a resource with only one morphology, or when searching only the Hebrew portions of a Hebrew Bible. Furthermore, we will also infer the morphology based on the text script where possible, e.g. lemma:λόγος and lemma:λόγος@N, when the most preferred available Greek morphology matches the morphology of the references.
Note: the lemma:λόγος@N,... syntax is shorthand for an ANDEQUALS search. It is possible to perform the same search using the explicit syntax: (<Lemma = lbs/el/λόγος> ANDEQUALS (<LogosMorphGr ~ N????>, ...))
Automatic untransliteration will no longer be constrained to a single language. You can still limit the results by explicitly prefixing the text, e.g. g:logos, a:mlk, h:mlk.
Note: morph searches in visual filter documents are unchanged.
Passage Guide
Added the ability to select a particular number of commentaries to load, this can be set in your template or by clicking settings entering the number of commentaries you want to see in this section, then right clicking on the commentaries header and selecting refresh.