Search results

==Front-end Bible study applications== * [[Frontends:The_Bible_Tool|The Bible Tool]] web server application

...ion of a module that would not match the default versification for the KJV Bible is to decide which of the several versifications is most suitable for the n We will accept only plain texts or texts marked up in OSIS or TEI, with the sole exception texts based on CCEL documents that are mark

...modules and LexDict modules in IMP format. Bibles must be in either VPL or OSIS format. ...ture reference links in OSIS or ThML All other modules need to be in valid OSIS or TEI XML files before submission is accepted.

: SourceType=OSIS ....\par Inquiries and comments may be directed to:\par\par CrossWire Bible Society\par kjv2003@crosswire.org\par http://www.crosswir

...JSword|JSword]] based installer (e.g. as used for [[Frontends:BibleDesktop|Bible Desktop]]), which uses HTTP access. == CrossWire Bible Society ==

...] in his New Testament published in Geneva in 1557.<ref>See page 89 of the OSIS 2.1 User Manual.</ref> ...iki/Biblical_canon Canon] pertains to what is included in a version of the Bible.

...es (such as those on CCEL) into valid OSIS, as losslessly as possible. The OSIS can then be used for creating SWORD modules. See the README in the relevan === OSIS Book Abbreviations ===

What follows is a list of abbreviations for books of the Bible, for use with OSIS and Sword as standard book IDs. The basis for most of these works is the

...t to see a new module, your quickest results will come from encoding it in OSIS yourself and submitting that to us. ...ed the Pentateuch, and Jonah, and other books later published in Matthew's Bible (Book of Joshua, Judges, Ruth, First and Second Samuel, First and Second Ki

==OSIS== ..., making it difficult when they wish to share in service with each other. OSIS provides a common markup for multiple visions.

= Syntax Check and Valid OSIS/TEI files = An OSIS or TEI test is an XML Document that must be:

CrossWire Bible Society respects [[copyright]]. As such, conversion of material that is un ...supports currently and actively the following markup for module creation: OSIS, [https://tei-c.org/ TEI], ThML and plain text.

In SWORD a commentary is structured just like a Bible. The difference is that instead of verse text the commentary has discussion To produce an OSIS Commentary, you can use this template:

...at furthering the Kingdom of our God. We are also a resource pool to other Bible societies and Christian organizations that can't afford --or don't feel it' ...w wirelessly). Our Scripture distribution compares with the largest of the Bible Societies listed.

...tive P5] markup is encouraged. TEI P5 is an XML standard, quite similar to OSIS and ThML, intended for encoding all types of electronic documents. Since TE ...uments. Our customized TEI schema is available at http://www.crosswire.org/OSIS/teiP5osis.2.5.0.xsd.

* Bible reading ...nks (display & toggle)<ref>Currently in SWORD, there is no separate Global OSIS filter for OSISDictionary.</ref>

=== Bible Modules === |Whole Bible

...to provide a complete, though not exhaustive, account of how to encode an OSIS genbook to become a SWORD module. ...hich are parallel to each other. For a complete OSIS XML file, see Example OSIS Genbook below.

...mat of SFM is simply plaintext with backslash(\) codes. For example, a new Bible verse is signaled by '''\v''' followed by the number of the verse. ...us dialects of SFM can still be found. It was common for various agencies, Bible societies, and even regional offices of such groups to have their own SFM s

* '''1.7''': New notes with bible references (2007.08.29) There are two whole Bible downloads available from Bibliquest:

...e_interface command line interface] (CLI) front-end to the SWORD Project's Bible software library. Essentially, "diatheke" is the stuff contained within the |for modules with footnotes (GBF/ThML/OSIS)

...en 43 Bibles by Wycliffe. Some of the Bibles belong to WBTI, others to the Bible League. ...zip contained OSIS files, a separate file for each book of the Bible. The OSIS files were not all valid at the time of delivery. The contents of the files

=Creating a Basic OSIS Document= [http://crosswire.org/osis/tutor.jsp Creating a basic OSIS document] can be an easy task with just a little direction, which this brie

osis2mod transforms an OSIS encoded [[OSIS Bibles|Bible]] or [[OSIS_Commentaries|commentary]] into a SWORD module. * Added reporting of unhandled entities. (An OSIS document should not have entities other than the canonical 4 entities.)

...sed for a module named [MyModule], depending on<BR>(a) the type of module (Bible text, commentary, lexicon or dictionary<ref>Daily devotionals & glossaries ...Bibles having entries greater than 64K bytes)<ref name="text4">e.g. If the Bible contains large introduction sections</ref><br/>

*'''AB''' &mdash; [http://code.google.com/p/and-bible/ And Bible] based on JSword, for Android OS *'''ABS''' &mdash; [http://www.kiyut.com/products/alkitab/ Alkitab Bible Study] based on JSword, uses Java 5+

'''General Bible Format''' ''(deprecated)'' ...le search programs. The complete specification is at http://www.ebible.org/bible/gbf.htm.

This page contains an example OSIS document that is structured by Book-Section-Paragraph. == OSIS Bible Example (BSP) ==

...Is. This necessitates having a standard for new and existing front-ends. A Bible URI standard is also necessary for [[Frontends:Bookmarks_Standard|Bookmarks ...///Gen.1.1''' -- an empty module between // and / (implies use of whatever Bible module is current, or default).

...ke Go Bible for feature phones are now well past their peak popularity. Go Bible is no longer being actively developed. == Collaboration between CrossWire and Go Bible ==

...recording potential change requests to the [http://bibletechnologies.net/ OSIS] 2.1.1 XML schema, and for defining our own updated schema. ==Bible Technologies Group==

...source multiplatform collaborative USFM editor, useful for correcting USFM Bible source texts ...checking XML syntax and validation, e.g. to an external schema such as for OSIS. XMLTools also has various options to "pretty print" and linarize (sic) the

...Bible Creator''' is a software tool for converting Bible texts into '''Go Bible''' Java ME applications that can be loaded onto suitable mobile phones. Go Bible Creator is a '''Java''' application and requires [http://www.oracle.com/tec

...you can safely get rid of the on-screen virtual keypad and retain full Go Bible functionality, thus taking advantage of the full area of the screen for the ...rizontal touch screen scrolling navigates to next/previous chapter. The Go Bible Menu is accessed by touching anywhere in the top bar.

See [[Projects:Go Bible#AutoIt_Scripts]]. ''Peter has had some success in converting ABW files to OSIS using scripting tools''.

...e is intended to be a one-stop reference which lists all the extensions to OSIS either recognized by the SWORD API or (at least) also found in various SWOR The OSIS reference standard permits custom extensions to XML elements in the form of

* osis -- OSIS docs for osis2mod or sharing with publisher/3rd parties * gobible -- compiled Go Bible applications (including any smaller collections)

* WBTI denotes Wycliffe Bible Translators International * BL denotes Bible League

...n strings for anything you might want. REQUIRED are the book names of the Bible, including deuterocanonical books if used. Other things might be option nam ...n specifies all possible alternative book names and abbreviations for each Bible book. These are required for the locale to work correctly within the SWORD

BibleSync is a multicast protocol to support Bible software shared co-navigation. It uses LAN multicast in either a personal/s This library is not specific to any particular Bible software framework, completely agnostic as to structure of layers above Bib

Corrected anomalous OSIS highlighting output w/GHellings' patches in src/modules/filters/osis{plain,xhtml}.cpp

...is the only module maintained by CrossWire volunteers. It is marked up in OSIS XML. All other modules are based on source text from external providers. * The Strong's numbers in the OT were obtained from [http://www.bf.org/ The Bible Foundation]

The name has to be set in CamelCase format. Example for The French Bible David Martin 1707: <code>FreBDM1707</code><ref name="bdm">The published yea * OSIS: <code>.osis.xml</code>