A USFM Bible editor using the BibleOrgSys library and Python's tKinter windowing library for simple and easy installation. (It's all in the standard CPython install.)
On most systems, Biblelator can be installed (as shown above) with:
`pip install Biblelator`
but if it complains, maybe:
`python3 -m pip install Biblelator`
The app can be run from the command line with:
`Biblelator`
which should start up and display a smallish window, or to view all the available options:
`Biblelator --help`
You can discover the program version (doesn't match the package version) with:
`Biblelator --version`
Biblelator reads or creates a BiblelatorData folder in your home folder.
Log files are stored in a subfolder there and may be useful for reporting errors.
(If you have start-up problems, you might want to edit the settings there,
or even delete the entire settings file if you have no complex saved windows settings yet.)
Because some Bible users need to remain anonymous, Biblelator defaults to no internet use.
However this reduces functionality, and most users will want to run the program once,
and then close it and edit the Biblelator.ini file created in the BiblelatorData/BiblelatorSettings folder
and change internetAccess to Enabled.
While there, you might as well update the currentUserName and other entries
under [Users].
The other auxilliary apps included are BiblelatorSettingsEditor,
BOSManager (for inspecting Bible Organisational Systems), and
SwordManager for viewing
and downloading Sword modules.
(All three are at various stages of incompleteness.)
NOTE: This packaging is still being tested following massive restructuring, and is not necessarily fully functional until it is marked as v0.1.0 or higher when some open-licensed resources will also be downloadable. We also have hopes to improve documentation before v0.2.0. After that point, we also hope to release some prepackaged versions— probably including Docker and Snap.
This software has been developed in very small chunks of spare time since 2013 (so it's not necessarily well structured, and definitely not polished). However, it was used as my main Bible editor instead of Paratext for a couple of years.
This package will not reach v1.0.0 until after the BibleOrgSys reaches it. The API will not become fixed/stable until the v1.0.0 release.
No attempt at all has been made at memory or speed optimisations and this is not planned until after the release of v1.0.0. So if it becomes very slow, you might need to close some Bible resource windows.
Biblelator is developed and tested on Linux (Ubuntu) but should also run on Windows and OS X (although not so well tested).
See https://ubsicap.github.io/usfm/ for more information about USFM.
Metadata
Release files for Biblelator 0.0.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| Biblelator-0.0.8.tar.gz | 476.8 kB | Without provenance | Details for Biblelator-0.0.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| Biblelator-0.0.8-py3-none-any.whl | Python 3 | none | any | Details for Biblelator-0.0.8-py3-none-any.whl |
Total release size: 989.4 kB
Release files / Biblelator-0.0.8.tar.gz
| Download URL | Biblelator-0.0.8.tar.gz |
|---|---|
| Size | 476.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fa9b644bc186ca1e41c536cc5d6267ff0eed4c30fab775dde77c7a857578873a
|
|
BLAKE2b-256 checksum How to use checksums |
3f453f2666ba26106f7b01f66a9d3029921c55b623db21cbf5b4aae24abb9b5e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/47.1.1 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/3.8.2
|
Release files / Biblelator-0.0.8-py3-none-any.whl
| Download URL | Biblelator-0.0.8-py3-none-any.whl |
|---|---|
| Size | 512.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
52f174cb9f0a2f2b46b26cba3a42b10ef1bf85e9cdc3424d8240437df3dacac2
|
|
BLAKE2b-256 checksum How to use checksums |
b6f12984fbca6ffc00e94f32e1ef62be2a1d9e1afa5f8d5068b7a85f49c34eb4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/47.1.1 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/3.8.2
|
Security for Biblelator 0.0.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.