Details
-
Type: New Feature
-
Status: Closed (View Workflow)
-
Priority: Major
-
Resolution: Won't Fix
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
Description
I saw your note re plans to create a new USFM to OSIS importer.
May I make the suggestion to make this a BCV rather than a BSP importer?
The reasons
1) carefully imported they should look the same in all frontends.
2) No frontend ever supported sections as a method of addressing chunks
of texts, nor is any likely. Sections and paragraphes are important
presentationally + exegetically, but really do not offer us much in
terms addressing/programming.
3) The ongoing osis2mod saga is not ever going to get resolved, I guess,
so a format closer to the internal format will allow us to consider
alternative ways to move from OSIS to a module.
4) Having an XML format where verses are addressable via XPath improves
the ability to postprocess OSIS files. I am working slowly on various
"upgrades" we can do on PD modules - cross references, WoJ markup,
possibly eventually in some form Strongs. There is a need for study
bibles in many languages and this is my attempt to provide such or make
provision easier than it is now.
5) Equivalence of commentary and bible module - this would allow us to
import USFM encoded commentaries/study bibles in a better way.
I am sure there are more.
I could come up with no reason why we should prefer the existing BSP import.