This seems to be a bug with the order in which some audio sets are indexed. I modified the path parsing code some which may take care of it. I will upload an updated Bible Analyzer exe in a day or two to try out.
Ruben, I found the issue with the Strong's Index. Some Strong's numbers represent words that are not translated into English and those that were at the start of a verse were misindexed. I modified the code and think the issue is fixed now. Here is a new StrongsEx, http://www.BibleAnalyzer.com/files/...
The default Verdana font does not have that character and a few others, however other font sets, such as Segoe UI, does have it. You can change the default font in Preferences. There is not much that can be done about the high DPI issue until the toolkit developers provide the feature. Progress can ...
Robert, I am working on the 5.3 Linux edition and may be able to work around the blue color issue. GTK3, which was introduced with 18.04 has caused some other issues. One of the main ones is RTL display of Hebrew texts. They made a change in GTK3 that the platform Bible Analyzer uses (wxWidgets/wxPy...
No, not yet. It is the underlying toolkit (wxPython) that controls the display resolution but the wx developers are working on it from what I understand.
Fonts are pretty much up to personal preference. We use the Galaxie Unicode fonts primarily in Bible Analyzer. We even ship them with the two Word Study Bundles. They have a pretty complete character set and render Hebrew and Greek characters uniformly.
Here is an updated .exe (v5.3.0.21). Just download and place in your existing Bible Analyzer portable folder. http://www.bibleanalyzer.com/files/bibleanalyzer5.exe This new beta fixes Verse syncing issue in ScripturePad Highlighting one word offset when note added to verse. Font gets larger when doi...