bibleget-i-o / bibleget-msword-addin Goto Github PK

Just today I noticed that the 3.0.1.8 installation package released October 4, 2020 is not working as expected. Someone asked me to re-install for them, and I see that the installation package is showing as "v2.0.0.0" ??? When launching, it is giving an error about something being invalid.
I tested on another workstation, and I found the same error:

Error reading setup initialization file

What is going on here? Has the installation package from sourceforge ever worked? I'm sure I tried the package before it was published to sourceforge, what happened in the meantime?

The latest working package that I have installed on these two workstations is v3.0.1.6 .

Since most Catholic versions of the Bible offer both Greek and Hebrew versions of certain Bible texts (such as the Book of Esther), the API now accounts for this by offering a new parameter preferorigin.

We need to account for this when retrieving a quote by giving the option to prefer the Greek or the Hebrew origin.

This will also require usage of v3 of the API endpoint.

I recently started getting this error message every time a request is issued to the server, effectively preventing the plugin from working at all: Request canceled: cannot create a secure SSL/TLS channel. Confirmed in v3.0.1.8 on two different machines on two separate networks. Needs to be fixed ASAP! I wonder if it only happens for v3.0.1.8 or for all versions?

In order to make it clearer that selecting the Bible versions in the "information about this plugin" popup window will not have any effect and will not change user preferences, the Select was simply set as readonly. So the single items are no longer selectable.

However this has had the adverse effect that the scrollbar no longer works, and now that we have added the Spanish version, it is cut off and not visible, and there is no way to scroll down the list.

We will either have to make the list somehow scrollable but not selectable, or we will have to make it taller...

The auto update mechanism does not seem to be working ever since we switched to sourceforge.
Of course it wouldn't have worked right away, because we needed a new way of identifying the latest release, no longer using the WordPress Download Manager API.
At first there didn't seem to be a way to identify the version number for the latest version in the sourceforge API, so I initially opted to use the Github releases API. However, the sourceforge support told me that even though it's not possible to tag the latest release with metadata about the release version, this can still be done by putting each new release into a folder that identified the version for that release. Then using the sourceforge API for the latest release, the version can be parsed from the path to the release.
I thought I had this taken care of, however I have not yet received a notification about a new release. So some debugging needs to be done.

on a Windows 10 machine with Office 2013 and v3.0.1.8 of the plugin, I suddenly started getting this error when trying to retrieve a Bible quote or search for verses by keyword:

The request was aborted: Could not create SSL/TLS secure channel

Not sure why this just started happening now...

When a non-accented term is used to search for verses, MySQL Fulltext search automatically produces results for both accented and non-accented versions of the term.

However, the highlighter (i.e. addMark() function), only matches exact correspondences or "downgraded" results (i.e. it will match a non-accented word in the Bible verse for an accented search term, but it will not match an accented word in the Bible verse for a non-accented search term, which we could call an "upgraded" match).

This was solved recently in the Google Docs add-on by adding a function addDiacritics() alongside the stripDiacritics() function, and an addBMark() function alongside the addMark() function. The addBMark() function will filter out results already handled by the addMark() function so as not to interfere with the highlights already produced by this last function. And therefore the addBMark() function is called directly inside the addMark() function, to finish highlighting any results not already highlighted by the addMark() function.

See the following commits from the Google Docs add-on:

• BibleGet-I-O/BibleGet-Google-Docs-Addin@4a6f383
• BibleGet-I-O/BibleGet-Google-Docs-Addin@a1a6099
• BibleGet-I-O/BibleGet-Google-Docs-Addin@cb3da62
• BibleGet-I-O/BibleGet-Google-Docs-Addin@f1ed3ef