-
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
...2.1 is now the preferred format for Bibles and commentaries. At the moment OSIS does not have thorough support for complex dictionaries. For that reason we
14 KB (2,376 words) - 20:31, 4 June 2020
-
...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.
3 KB (576 words) - 16:29, 11 March 2018
-
: BlockType=BOOK
: SourceType=OSIS
9 KB (1,381 words) - 06:47, 14 February 2020
-
...] in his New Testament published in Geneva in 1557.<ref>See page 89 of the OSIS 2.1 User Manual.</ref>
...ed into the engine in the form of the file <tt>canon.h</tt>, which offered book names and chapter + verse offsets to the engine. The new approach is that:
11 KB (1,634 words) - 18:02, 29 June 2020
-
...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
To create ThML cross references out of (<Book> <Chapter>:<Verse>) type references:
4 KB (585 words) - 18:22, 10 January 2018
-
OSIS and Sword as standard book IDs. The basis for most of these works is the
To the extent possible, Paratext abbreviations have been given for each book, based in large part on BFBS' data<ref>Rees, Neil. ''Analysis of canonical
12 KB (1,905 words) - 02:11, 3 September 2012
-
'''xml2gbs''' 1.0 is the OSIS/ThML/TEI General Book module creation tool for the SWORD Project.
...internal structure that seems to deviate from the strict specification for OSIS. For example, the output of '''mod2imp BaptistConfession1646''' contains th
5 KB (591 words) - 21:13, 9 June 2023
-
...t to see a new module, your quickest results will come from encoding it in OSIS yourself and submitting that to us.
...Pentateuch, and Jonah, and other books later published in Matthew's Bible (Book of Joshua, Judges, Ruth, First and Second Samuel, First and Second Kings, a
66 KB (9,963 words) - 06:09, 23 July 2024
-
==OSIS==
..., making it difficult when they wish to share in service with each other. OSIS provides a common markup for multiple visions.
45 KB (7,193 words) - 07:21, 23 July 2023
-
...supports currently and actively the following markup for module creation: OSIS, [https://tei-c.org/ TEI], ThML and plain text.
* [[osis2mod]] – imports Bibles and commentaries in OSIS format to SWORD format [http://crosswire.org/ftpmirror/pub/sword/utils/win3
8 KB (1,308 words) - 12:11, 20 February 2021
-
...p://en.wikipedia.org/wiki/XSL_Transformations XSLT] script to convert such OSIS XML files to the format suitable for Go Bible. [[Projects:Go Bible/Go Bible
3 KB (567 words) - 12:30, 28 April 2018
-
* Easy navigation from one book/chapter to the next/previous.
...nks (display & toggle)<ref>Currently in SWORD, there is no separate Global OSIS filter for OSISDictionary.</ref>
12 KB (1,861 words) - 15:17, 10 January 2018
-
...tains an XML document preamble <xml encoding="UTF-8" version="1.0"> <osis xmlns=".....<br>Maybe it was built with imp2mod and not osis2mod?
...ms to be missing Deut 34:12 which shows up in released TSK. This is end of book content.
14 KB (2,005 words) - 16:41, 9 March 2020
-
...ilestoned chapters in between. Once milestoned chapters are used anywhere, OSIS "requires" that they are used everywhere. If quotes are not marked up, then
...chapters and the latter for any other type of chapter in any other type of book. Similarly <p> and <div type="paragraph"> have different meanings. A
18 KB (2,947 words) - 12:19, 5 February 2019
-
...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.
11 KB (1,715 words) - 10:21, 19 December 2020
-
...ively pursued by CrossWire developers. New content should be encoded using OSIS.''
...for modules encoded with ThML and OSIS, each verse, dictionary entry, and book division needs to be well-formed XML or it will result in display problems
2 KB (292 words) - 12:38, 8 January 2018
-
* '''1.12''': Correct note references when in same book (2008.01.10)
...D) developped a tool to convert the text source (encoded in HTML) into the OSIS format, available on [http://koocotte.org/darby/ koocotte.org/darby]. and o
7 KB (907 words) - 10:28, 18 May 2019
-
* Change osis2mod to accept a wider range of valid OSIS inputs, creating a module that the SWORD Engine can handle, specifically al
* Change the module so that it is encoded as recommended in the wiki for OSIS Bibles. Then it can work with 1.5.9
27 KB (4,527 words) - 17:30, 11 February 2021
-
...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
...e provided zips and output a modifiable table-of-contents file listing the OSIS books in their canonical order. (The converter outputs a list based on alph
9 KB (1,468 words) - 15:11, 16 June 2012
-
=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
16 KB (2,414 words) - 19:59, 8 January 2018
