Download the PHP package stevenbuehner/bible-verse-bundle without Composer
On this page you can find all versions of the php package stevenbuehner/bible-verse-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download stevenbuehner/bible-verse-bundle
More information about stevenbuehner/bible-verse-bundle
Files in stevenbuehner/bible-verse-bundle
Package bible-verse-bundle
Short Description A highly tested library to parse, identify, merge store and work with bibleverses.
License MIT
Homepage https://github.com/stevenbuehner/BibleVerseBundle
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package bible-verse-bundle
What is it?
With this bundle you get an incredible powerful backend to parse any text and identify bible verses within it. It works with symphony but also with any other composer system. The bible verses are not only recognized, but intelligently seperated into book, chapter and vers-ranges.
I am using it in a big installation to store and index bible verses in the database and perform very quick and complex searches.
Features
The library recognizes all kind of different texts as bible verses in german and in english. For example:
-
1Tim 3,16
- 1 Tim 3,16f (one following verse)
- 1 Tim 3,15-16 (multiple verses as range joined by "-")
- 1 Tim 3,16ff (following verses with "ff" until to the chapters end)
- 1 Timotheus 3,16 (long naming convention)
- 1 Tim 3,15.16 (multiple verses joined with ".")
- 1 Tim 3,15+16 (multiple verses joined with "+")
- 1. Timothy 3,16 (preceding "1." convention)
- I Timothy 3,16 (preceding "I" convention / with or without ".")
- First Timothy 3,16 (preceding "First" convention)
- 1st Timothy 3,16 (preceding "1st" convention)
- 1.Timotheusbrief 3,16 (german long naming convention)
- 1 Ti 3,16 (different short naming conventions)
- 1Tim 3,16-4,2 (ranges over multiple chapters)
- 1Tim 3 (whole Chapter)
Examples
The texts are recognized and parsed into valid integers. For 1Tim 3,16-17 this would be:
| Parsed-Text | Book-Id | From Chapter | From Verse | To Chapter | To Verse |
|---|---|---|---|---|---|
| 1Tim 3,15-16 | 54 | 3 | 15 | 3 | 16 |
| 1Tim 3,15f | 54 | 3 | 15 | 3 | 16 |
| 1Tim 3,16-4,2 | 54 | 3 | 16 | 4 | 2 |
| 1Tim 3 | 54 | 3 | 1 | 3 | 16 |
| 1Tim 3-4 | 54 | 3 | 1 | 4 | 16 |
Storage and search optimization
Internally the bible verses are stored as two numbers which describe a range (start - end). This makes it possible so index bible verses and search for intersecting bible verses super quickly.
START and END are set together as three-digit codes:
| Book-ID | Chapter-Number | Verse-Number |
|---|---|---|
| (three digits, zero padded) | (three digits, zero padded) | (three digits, zero padded) |
Which results in this indexing:
| Parsed-Text | Book-Id | From Chapter | From Verse | To Chapter | To Verse | START | END |
|---|---|---|---|---|---|---|---|
| 1Tim 3,15-16 | 54 | 3 | 15 | 3 | 16 | 054003015 | 054003016 |
| 1Tim 3,15f | 54 | 3 | 15 | 3 | 16 | 054003015 | 054003016 |
| 1Tim 3,16-4,2 | 54 | 3 | 16 | 4 | 2 | 054003016 | 054004002 |
| 1Tim 3 | 54 | 3 | 1 | 3 | 16 | 054003001 | 054003016 |
| 1Tim 3-4 | 54 | 3 | 1 | 4 | 16 | 054003001 | 054004016 |
Usage
Parsing text to BibleVerses Entities
Formatting BibleVerses Entities as Text
Language German and English are supported by default
Extracting bible verses as BibleVerse entities from larger texts
Join multiple BibleVerse Entities together
Accessing BibleVerse start and end number
BibleVerse Interface
Bible verses are valid BibleVerseInterface instances. Which means they can be extended and come with these default functions
JavaScript
There is also a JavaScript library for parsing bible verses and use it i.e. for markdown purposes.
Generating Javascript-Library-Updates
The JavaScript library is generated with the command:
