Bible Word Study - word selection issue

If I select a word which has a footnote (superscript letter) immediately before it, the footnote leter becomes the first letter of the word selected.

e.g. Psalm 30:12 in ESV has a footnote letter "n" immediately before the word "glory". When I select and hold the word "glory" the word "nglory" is selected in Bible Word Study pane.

Find more posts tagged with

Mobile App

Comments

Graham Criddle

Hi Murray

On my HTC Esteem HD, when I try this the word "glory" is shown in the Bible Word Study pane seemingly correctly but no information is displayed when I complete the search.

It is as though the "n" is there but not visible.

Graham

David Stevely

https://community.logos.com/discussion/comment/274369#Comment_274369

On Asus Transformer same result as Graham.

David

Dave Hooton

When I select and hold the word "glory" the word "nglory" is selected in Bible Word Study pane.

Same problem occurs in Beta 10 on my Samsung Galaxy S, the following appears in the pane (?) at bottom of screen:

nglory

Text glory

MSS

Lemma

etc.

Dr. Rupert Loyd Jr.

https://community.logos.com/discussion/comment/279341#Comment_279341

Great functions for the Word study in Beta 10. It is going to be terrific.

I notice a problem with word selection in NA 27 and SBL Greek. A long press calls up the word directly to the left of the word I pressed on my HTC Evo. I did this consistently through both SBL, and NA 27.

Additionally, in the NET bible, a long press on a word with footnote attached results in a search that includes the number attached to the word. Ex: the word "Spirit" with a blue footnote attached yields Spirit31 for a search.

Hunter Clagett

If I select a word which has a footnote (superscript letter) immediately before it, the footnote leter becomes the first letter of the word selected.

e.g. Psalm 30:12 in ESV has a footnote letter "n" immediately before the word "glory". When I select and hold the word "glory" the word "nglory" is selected in Bible Word Study pane.

Thank you for bringing this to our attention! I have submitted this bug to our bug tracking system and we should be pushing out a fix in a future release.

Thanks,