Search results

...] in his New Testament published in Geneva in 1557.<ref>See page 89 of the OSIS 2.1 User Manual.</ref> * [http://en.wikipedia.org/wiki/Biblical_canon Canon] pertains to what is included in a version of the Bible.

OSIS and Sword as standard book IDs. The basis for most of these works is the The intent of this list is to provide abbreviations for all texts

Here is a place to request modules you would like to be made. If the copyright holder has been contacted, the permissions grante ...st results will come from encoding it in OSIS yourself and submitting that to us.

This page lists some of the more common file formats ''relevant'' to The SWORD Project, associated utilities, and other CrossWire projects. ...ocument it and certainly no need to stick to it. We change it when we need to. We therefore do not encourage direct interaction with it, but firmly recom

...Bibles for printing and display in programs like [http://paratext.org/ UBS Paratext]. The format is popular among Bible translation agencies and Bible societie ...longside [https://pt8.paratext.org/2016/11/09/paratext-8-beta-is-released/ ParaTExt version 8.0]).

...Wire and Go Bible volunteers, in effect to enable the Go Bible application to act as something like a front-end for CrossWire Bible modules on the Java M ...reason for this is that Java ME applications that require even read access to separate data files nag the user repeatedly for permissions.

....com/shared/c1bejb254p David's Box folder]<ref>As a consequence of changes to Google support for its code pages, after January 2014, the binaries for fut Before Go Bible Creator can be used you will need to obtain or create suitable source text containing the Bible translation or B

...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 ...with the prefix '''x-'''. <ref>In rarer cases, the x-prefix has been used to define an ''attribute name'' or even an ''element name''.</ref>