Follow-up to thread => Highlight the words of God in the Old Testment found two proximity searches not highlighting using Logos 6.2 RC 3 on Windows 7:
Keep Smiling [:)]
I don't think proximity searches are meaningful with {Speaker}. Much better is something like am WITHIN {Speaker <Person God>}.
The absence of highlighting with {Speaker} text is due to words that are inserted for the translation, although some like 'abundantly' in Gen 1:20 are due to FL tagging errors.
The absence of highlighting with {Speaker} text is due to words that are inserted for the translation,
Ideal resolution would be {Speaker} tagging of inserted words.
I don't think proximity searches are meaningful with {Speaker}.
For words inserted for translation, proximity search is useful for highlighting. Caveat: some words immediately follow end of {Speaker}: (e.g. and, then) so are a bit challenging to highlight.
For words inserted for translation, proximity search is useful for highlighting.
As a workaround I see what you mean
Found four more proximity searches not highlighting using Verbum 6.2 on Windows 7:
For LEB, workaround visual filter is currently OK for highlighting from Genesis 1 through Leviticus 12; shared "{Speaker <Person God>}" visual filter with "Logos Visual Filters" group. From Genesis 1 through Exodus 22, am aware of five highlighting bugs so workaround filter appears viable for many verses.
Edit: learning ESV is a bit more difficult for work around highlighting. An example is "in the" found in Genesis 15:16 An NRSV example is "The land of" that begins Genesis 15:19 Both of these phrases are not found with BEFORE 1 WORD {Speaker <Person God>}
In NASB 95, cannot highlight "vessels of" stone in Exodus 7:19 using Verbum 6.2
Edit: in 2011 NIV cannot highlight "the face of" in Exodus 10:5
Overall am amazed how many words added for translation can be highlighted while wishing that Speaker label included added words.
Bump - 2aa
Word proximity can't work when the {Speaker} results include Hebrew text that has no corresponding English words. This is by design.
You could try using character proximity.
Thanks, my To Do list includes revamping visual filter with some CHAR proximity:
