Jump to content

Word alignment issue in Greek Bible


miketisdell

Recommended Posts

In Rev. 16:1, the cursor location and the selected word are one word off. This corrects itself in Rev. 16:2.

In the screen capture provided you can see the location of the hovered cursor, and the highlighted word do not match.  Note: when I did the screen capture the cursor changed form from the text icon to the arrow icon. When I am using accordance it is the text icon that is seen. 

post-35053-0-42345400-1550944714_thumb.jpg

  • Like 1
Link to comment
Share on other sites

There are also some other parts in this Bible with the same problem. I want to wait till a new version is out to report it but since Mike has started it I jump in. 

 

As I see you are on a Win so it is not only on my Mac. 

 

Same on Gen 2:1; Gen 3:1; Gen 6:1; Gen 9:1 as far I checked for 2 minutes, there are surely more.

 

and don't forget; LXX-GNT and the normal LXX module the bug is on both.

 

This bug relates to others I have started with similar patterns. And please fix the crasis too.

 

Greetings

 

Fabian

Link to comment
Share on other sites

Must be an issue related to Windows. I'm not seeing that behavior on the Mac. 

Link to comment
Share on other sites

I am on my ThinkPad. When I get home, I can test it on my MBP.

Link to comment
Share on other sites

Yep it's some sort of module related issue - WH shows it - EPT does not. But only if you have the text pane display set to paragraph. Separate verses doesn't show it.

 

Thx

D

Link to comment
Share on other sites

Must be an issue related to Windows. I'm not seeing that behavior on the Mac.

My bug is on two Macs!

 

Greetings

 

Fabian

Edited by Fabian
Link to comment
Share on other sites

My bug is on two Macs!

 

Greetings

 

Fabian

 

Wow, that's interesting. Have you tried uninstalling those texts and reinstalling? 

Link to comment
Share on other sites

I've tried it again with the LXX-GNT on the MacPro which is before me. 

 

No success.

 

Greetings

 

Fabian 

Link to comment
Share on other sites

I think I've tracked this down. I couldn't replicate this issue in Accordance 12.2.9, but it's happening in the current release version. However, it's resolved in the current beta on both Windows and Mac, so a fix will be coming very soon.

Edited by Mark Allison
Link to comment
Share on other sites

  • 4 weeks later...

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...