More powerful options for searching Bible references

The present search methodology is quite restrictive and doesn't catch the variety of shorthand spellings that people use. For example, when a person references the book of Matthew, they might say

Mt 13:12 or Matt 13.12 or Mat. 13:12, or even Matthew 13:12.

Furthermore, sometimes a bible service website will have their own shorthand, as for example BibleHub.com does not support Camel Case, so a text-transform to lowercase is needed in the urls.

1. A CSV upload and processing feature:

First column is the official book name that is used in the generated urls. Any subsequent column on that row is a valid name that maps to that name. Eg:

Matthew,Mt,Mt.,mt,mt.,matt,matt.,Matt,Matt.
Songs,Songs of Solomon,Songs Of Solomon,songs of solomon,sos,SoS,SOS,songs,sgs

There should be one master CSV record, that is used for all services, and the user should be able to download, edit and upload that file.

Each service must also allow a custom CSV to be used in preference to the master CSV.

Note: no locale-specific functionality is required in this feature. If a user wishes to match Matthew in Spanish as Mateo, they can achieve that by adding Mateo and mateo to the spreadsheet. If the website service they are using requires Mateo, then it should be spelled that way in the first column of the spreadsheet and Matthew should be placed in another cell on that row.

Create a comprehensive CSV as a starting point, that is permanently bundled in the extension and is processed as an upload to the master CSV record when the extension is installed.

2. Update the search algorithm to support period (.) separator or colon (:) separator, where presently it will only match a colon pattern. Eg:

Matthew 13.12 will not match, but it should, and Matthew 13:12 does match, as it should.