From CrossWire Bible Society
Jump to: navigation, search


osis2mod transforms an OSIS encoded Bible or commentary into a SWORD module.

Where to get it

Current status

Software bugs relating to osis2mod should be reported in http://www.crosswire.org/bugs/browse/API

Please describe current status of osis2mod, including a list of any outstanding issues or unsolved difficulties.

History of Changes

The following outlines in reverse chronological order the major changes to osis2mod. When several changes were made over the span of a few days, they are lumped into the most recent date. Bug fixes are not mentioned.

Date Revision Feature



  • Changed the handling of <div type="colophon"> to not convert it to milestones.
  • Added reporting of unhandled entities. (An OSIS document should not have entities other than the canonical 4 entities.)



  • Added support for large entries (> 64K) in compressed modules (aka zText4).
  • Added support for UTF-16 and SCSU using the -e flag. SCSU is experimental.
  • Added support for BZip2 and XZ compression, changing -z and -Z to -z <l|z|b|x>
  • Added support for compression levels of 1 to 9 using the -l [1-9] flag.



  • Changed the transformation of <p> from <div type="paragraph" sID="xxx"/> to <div type="x-p" sID="xxx"/> This is a semantic change that brings osis2mod into alignment with the OSIS specification.



  • Allow for XML comments to be in the document, but stripped from the module. This allows for large parts of a document to be commented out, which is especially important during development.
  • Allow for <p> elements to be in the <header> element but ignored. Previously, the p in a header, having been transformed to a div, was taken to be the start of the module's content.



  • Restored pre-verse handling. Titles no longer need to be specially specified in OSIS.



  • Removed pre-verse handling. Titles now have to be specially specified in OSIS. In OSIS there should also be no tags between verse elements except title and those marking book and chapter.



  • Improved handling of chapter introductions.



  • -d flags now always available.



  • Added -d flags as a compile time option.
  • Improved exit codes and documented them here.
  • Labeled all diagnostic and debug output.
  • Can now read from standard input.



  • Predictable handling of inter-verse material.
  • All tags, except verse, included in the module.



  • -v v11n added to support Alternate Versification.
  • -s <2|4> added to support uncompressed commentaries with large entries (exceeding 64K bytes).
  • Replace paragraph hack with milestoned paragraphs: <div type="paragraph" sID="xxx"/> ... <div type="paragraph" eID="xxx"/>



  • Words of Christ (WoC) can be marked up naturally. osis2mod does the right thing.
  • Container elements converted to their milestoned form.



  • Now supports commentaries in addition to Bibles.
  • Added utf-8 detection and automatic conversion from cp1252 and iso8859-1 to utf-8, making that the default behavior
  • Added NFC normalization, making it the default
  • Now handles the full definition of an osisID and an osisRef, including workID and grain.



  • Changed command-line parsing from positional parameters to flags.



  • All whitespace tokens are converted into blanks and adjacent spaces are merged into one. Leading whitespace on each verse is still removed.



  • Added version identification to the running of osis2mod.



  • Added ignoring of unknown books



  • Optimized writing to module.
  • Added simple transformations of <q> and <p> into milestones.
  • Now allow empty attributes, such as marker=""



  • Updated to support OSIS 2.1
  • Added validation that verses in isolation are well formed



  • Added command-line options for compress and encipher.



  • Removed <verse> and </verse>



  • Reverted pre-verse title handling



  • Removed pre-verse title handling
  • Added <verse> and </verse>
  • Added support for milestoned version of some OSIS elements
  • Added support for verses that are not in the KJV versification by appending them to the closest prior verse.
  • Added support for osisIDs with sub-verse references (i.e. osisID grains)



  • Added support for linked verses



  • Added recognition for <chapter> element



  • Initial version


Osis2mod performs the following transformations[1]:

  • Whitespace -- Allows for human-readable OSIS files.
    • Leading whitespace on books, chapters and verses is removed
    • Whitespace is normalized into blanks
    • Multiple adjacent whitespace is reduced to a single space
  • Unicode handling - All modules should be UTF-8, NFC (with the possible exception of Biblical Hebrew).
    • Latin-1 (cp1252 and iso8859-1) are converted into UTF-8
    • UTF-8 is normalized into NFC, unless specified otherwise (i.e. by using the -N option).
  • Milestone conversion - necessary for frontends to show a verse at a time.
    (note: genX is unique for an sID/eID pair, where X is a number.)
    • <q ...>...</q> is converted into <q sID="genX" .../>...<q eID="genX" .../>. Note: Quotes with who="Jesus" are not transformed at this time.
    • <p ...>...</p> becomes <div type="paragraph" sID="genX" .../>... <div type="paragraph" eID="genX" ...>.
    • <chapter ...>...</chapter> becomes <chapter sID="genX" .../>...<chapter eID="genX" .../>
    • <closer ...>...</closer> becomes <closer sID="genX" .../>...<closer eID="genX" .../>
    • <div ...>...</div> becomes <div sID="genX" .../>...<div eID="genX" .../> (as of r3401, <div type="colophon"...> is unchanged)
    • <l ...>...</l> becomes <l sID="genX" .../>...<l eID="genX" .../>
    • <lg ...>...</lg> becomes <lg sID="genX" .../>...<lg eID="genX" .../>
    • <salute ...>...</salute> becomes <salute sID="genX" .../>...<salute eID="genX" .../>
    • <signed ...>...</signed> becomes <signed sID="genX" .../>...<signed eID="genX" .../>
    • <speech ...>...</speech> becomes <speech sID="genX" .../>...<speech eID="genX" .../>
    • <verse ...>...</verse> becomes (when using -d 2 for debugging.) <milestone resp="v" sID="genX" ... />...<milestone resp="v" eID="genX" ... />
  • Words of Christ - necessary for front-ends to appropriately highlight the WOC, a verse at a time.
    • <q sID="XXX" who="Jesus" .../>...<eID="XXX" who="Jesus" .../> becomes <q who="Jesus" marker=""><q sID="XXX" .../>...<q eID="XXX" .../></q>
    • <q who="Jesus" ...>...</q> becomes <q who="Jesus" marker=""><q sID="genX" .../>...<q eID="genX" .../></q>
    • Within the following construct, <q who="Jesus" marker="">...</q> will surround verse text.
  • Pre-Verse Titles (obsolete with SVN revision 2358 for the SWORD 1.6.0 release and replaced with InterVerse Content)
    • Titles immediately preceeding a verse are converted into <title type="section" subType="x-preverse>...</title>
    • Interverse tags not in titles are appended to prior verse.
  • InterVerse Content (introduced with SVN revision 2358 for the SWORD 1.6.0 release)
    • InterVerse Content refers to all content not contained by the verse element.[2]
    • Such content is divided between the prior and the current verse.
    • Content appended to the prior verse is not marked in any special way.
    • Content prepended to the current verse is marked with <div sID="pvX" type="x-milestone" subType="x-preverse"/>...<div eID="pvX" type="x-milestone" subType="x-preverse"/>.


  1. These transformations are all performed "under the hood" as it were. Tweaking OSIS XML files to fix problems with pre-verse titles, etc., was never intended to be done by module developers as part of the preprocessing before using osis2mod.
  2. For OSIS files derived from USFM files, the implication of this requirement is the following rule:
    Do not place a title (or similar element) between a matching pair of verse milestones except where the translation places the title somewhere within the verse text in the USFM file.

Handling of Introductions, Titles and Inter-Verse Material

SWORD looks for module, testament, book and chapter introductory material. Those introductions can have appropriate titles as well. In SWORD 1.6.0 the handling of this material has changed.


  1. In the following, the effects of the above transformations are not shown. The tagging of the pre-verse material is also not shown.

Module and Testament Introductions

At this time, osis2mod does not fully support module and testament introductions. A module introduction should be place into testament 0, book 0, chapter 0, verse 0. A testament introduction should be placed into testament 1 or 2, book 0, chapter 0, verse 0. Currently, these are placed into Genesis 0:0 or Matthew 0:0.

Book Introductions and Titles

Book introductions and titles are straight forward. It includes the start of the book and everything following it up to, but not including the start of the chapter. See OSIS Bibles for best practices in marking up titles and introductions.

For example:

<div type="book" ...>
... introductory material ...

will put the following into the book introduction:

<div type="book" ...>
... introductory material ...

Chapter Introductions

Chapter introductions and titles are a bit problematic. Between the start of a chapter and its first verse, we could have a chapter title, a chapter introduction and/or a start of a section of verses or a titled verse. Osis2mod now handles this in a predictable fashion. From the start of the chapter up to and not including a section div or a title that has a type that is not main, chapter or sub, the content is chapter introduction. After that, it is part of the verse.

Specifically, the following list gives the possible first elements following the chapter introduction.:

  • <div type="section" ...>
  • <title type="yyy" ...> where yyy is not main, chapter or sub.

For example,

<chapter ...>
<title>Chapter Title</title>
<title type="sub">Chapter Subtitle</title>
<div type="introduction">... intro ...</div>
<div type="section">
<title>A section title</title>
<verse ...>...verse content...</verse>

will put the following into the chapter introduction:

<chapter ...>
<title>Chapter Title</title>
<title type="sub">Chapter Subtitle</title>
<div type="introduction">... intro ...</div>

will put the following into verse 1 of that chapter

<div type="section">
<title>A section title</title>
<verse ...>...verse content...</verse>

Between Verses

Between verses we may have closing tags to finish off what was started earlier, structural opening tags (e.g. line groups, divisions, paragraphs, ...), titles and/or introductory material.

Upon finding the close of a verse, osis2mod will append all adjacent closing tags to it. Once it finds a start tag, it will attach that to the following verse.

For example, suppose the following is between </verse> and <verse ...>:

<div type="section">
<title>Section title</title>

then it will append the following to the prior verse:


and will prepend the following to the current verse:

<div type="section">
<title>Section title</title>

Last Verse

The material following the last verse of a chapter is appended to that verse. You might find:

... verse content ...
<div type="colophon">... colophon text ...</div>


Only content starting the first <div> to the last </div> is retained. All other is excluded. From a practical perspective, this excludes the OSIS header information.


It is always preferable to use the most recent version of osis2mod and compiling it from SVN is best.


  1. After the SWORD 1.5.9 release, osis2mod was changed to take flags rather than positional arguments.
You are running osis2mod: $Rev: 3431 $
OSIS Bible/commentary module creation tool for The SWORD Project

usage: ./osis2mod <output/path> <osisDoc> [OPTIONS]
  <output/path>		 an existing folder that the module will be written
  <osisDoc>		 path to the validated OSIS document, or '-' to
				 read from standard input
  -a			 augment module if exists (default is to create new)
  -z <l|z|b|x>		 compression type (default: none)
				 l - LZSS; z - ZIP; b - bzip2; x - xz
  -b <2|3|4>		 compression block size (default: 4)
				 2 - verse; 3 - chapter; 4 - book
  -l <1-9>		 compression level (default varies by compression type)
  -c <cipher_key>	 encipher module using supplied key
				 (default no enciphering)
  -e <1|2|s>		 convert Unicode encoding (default: 1)
				 1 - UTF-8 ; 2 - UTF-16 ; s - SCSU
  -N			 do not normalize to NFC
  -s <2|4>		 bytes used to store entry size (default is 2).
  -v <v11n>		 specify a versification scheme to use (default is KJV)
				 Note: The following are valid values for v11n:
				   Calvin      	Catholic    	Catholic2   
				   DarbyFr     	German      	KJV         
				   KJVA        	LXX         	Leningrad   
				   Luther      	MT          	NRSV        
				   NRSVA       	Orthodox    	Segond      
				   Synodal     	SynodalProt 	Vulg        
  -h 			 print verbose usage text

See http://www.crosswire.org/wiki/osis2mod for more details.

Earlier builds (e.g. $Rev: 2893 $) also included the debug option help: See Debug Messages.

  -d <flags>		 turn on debugging (default is 0)
				 Note: This flag may change in the future.
				 Flags: The following are valid values:
					0   - no debugging
					1   - writes to module, very verbose
					2   - verse start and end
					4   - quotes, esp. Words of Christ
					8   - titles
					16  - inter-verse material
					32  - BSP to BCV transformations
					64  - v11n exceptions
					128 - parsing of osisID and osisRef
					256 - internal stack
					512 - miscellaneous
				 This argument can be used more than once. (Or
				 the flags may be added together.)

See http://www.crosswire.org/wiki/osis2mod for more details.

Parameters and Options

This a path to any existing directory. It is best for it to be empty.

This is a single, well-formed, valid OSIS document.

If - is used instead of a file name, the document will be read from standard input. This allows for two constructs:

  • Redirection
osis2mod ./modules/texts/ztext/KJV - < kjv.xml
  • Piping
cat kjv.xml | osis2mod ./modules/texts/ztext/KJV -

Osis2mod can create a Bible all at once or incrementally, depending on the presence of the -a flag. This provides for two abilities,

  1. Assembling a Bible from book files:
    mkdir /tmp/mymodule
    osis2mod /tmp/mymodule  matt.xml
    osis2mod /tmp/mymodule -a mark.xml
    osis2mod /tmp/mymodule -a rev.xml

    Note: The book files can be in any order. SWORD will order them correctly in the index.

  2. Adding corrections to a Bible:
    osis2mod /tmp/mymodule -a fixes.xml

    Note: When fixes are put into the module they are appended to the data file and do not actually replace the verses. The index file is adjusted to point to the new place in the data file.

-z <l|z|b|x>
A SWORD Bible can be compressed with Zip (-z z), LZSS (-z l), BZip2 (-z b) or XZ (-lx). All of CrossWire's compressed Bible and commentary modules are compressed with Zip. This saves significant space over an uncompressed module. Uncompressed modules are useful for debugging.

-b <2|3|4>
This setting is only useful for a compressed module. The choice as to whether to use Verse (2), Chapter (3) or Book (4, the default) level compression depends upon the amount of data in the block. A typical Bible is best compressed book by book. A commentary, chapter by chapter. If the commentary is very robust and the amount of text per verse is really huge, then verse compression might make sense.

All of SWORD's compressed Bible modules are compressed by book. Basically, all of the verses in a block are compressed and appended to the data file. For this reason, the datafile cannot be uncompressed by anything other than the SWORD and JSword libraries.

When creating the module by appending it is important to do so by whole compression block. That is, if blockType is Chapter, then the osisDoc needs to contain one or more whole chapters.

-l [1-9]
This setting is useful for a compressed module and provides the level of compression to be used. The default varies depending on the compressor used. The default is typically used.

-c cipherKey
This is typically 16 characters in length, having no leading or trailing spaces, consisting of alternating sets of 4 alpha and 4 numeric characters, such as Aduf0274PjNq0328. The key is case-sensitive.

-e <1|2|s>
This flag gives whether the input is to be converted to UTF-8, UTF-16, or SCSU. By default the encoding is UTF-8. Using UTF-16 is reasonable for non-latin texts with little markup. SCSU will compress the Unicode, but it has not been sufficiently tested, requires ICU support when compiling osis2mod and when running (not all frontends do).

All OSIS modules should be UTF-8 and all that are UTF-8 are also to be NFC. The default is to automatically detect the presense of Latin-1 (either cp1252 or iso8859-1) and convert it to UTF-8 and to normalize UTF-8 to NFC. This flag will turn off this behavior and is useful for creating Latin-1 modules or for modules for which the source text is already UTF-8 and NFC. It is also advised for Biblical Hebrew modules for which the source text (with accents and cantillation points) is intentionally not normalized, as "Unicode normalization can easily break Biblical Hebrew". Quoted from page 9 of the SBL Hebrew Font Manual.[1]

Note: this was added late Feb 2008 and requires ICU support when compiling.

-s <2|4>
A value of 2, the default, restricts modules to 64K bytes per entry. A value of 4, breaks this barrier. This is needed for Bibles, having large introductory materials, and for commentaries with large entries.

Note: 4 was added late Apr 2009 for raw, uncompressed modules and will be part of the SWORD 1.6.0 release (formerly known as 1.5.11). A later release extended support to compressed modules.

-v v11n
By default, osis2mod uses the KJV versification. The practical implication of this is that only books in the KJV canon are allowed and any text in an allowed book are retained. However, if the verse reference of a supported book falls outside of the versification it is appended to the prior verse in the canon. This flag allows for an alternate versification.

Note: This option was added in April 2009 as part of the SWORD 1.6.0 release.

-d flags
The flag can be used more than once or the flags can be added together. For example,

-d 2 -d 4

is the same as

-d 6

To do verbose debugging use:

-d -1

For the most part these flags are not intended for debugging modules, but rather for debugging problems in osis2mod.

The -d 2 flag produces no output but puts milestones into the module where verses start and end. The form of the milestone is:

<milestone resp="v" [attributes from verse] />

The milestone will contain the osisID from the verse and also a valid sID or eID. The sID/eID indicates the start of end of the verse.

Note: the -d 2 flag might change at any time, or may even be removed.


Osis2mod has robust, mind-boggling messages. These are provided here in hopes that it will help problem diagnosis.

Exit Status

When an error occurs that causes osis2mod to exit without processing the entire input file, a non-zero exit status is supplied to the caller. Here are the codes that osis2mod uses:

const int EXIT_BAD_ARG     =   1; // Bad parameter given for program
const int EXIT_NO_WRITE    =   2; // Could not open the module for writing
const int EXIT_NO_CREATE   =   3; // Could not create the module
const int EXIT_NO_READ     =   4; // Could not open the input file for reading.
const int EXIT_BAD_NESTING =   5; // BSP or BCV nesting is bad or improper XML comment

Diagnostic Messages

In the following, example values are given in [...]. The brackets do not actually appear in the message. Also, the messages are a bit prettier here than in reality.

WARNING(UTF8):     [ osisID ]: Should be converted to UTF-8 ([ text ])

The program will always check for text that is not UTF-8.

INFO(UTF8):        [ osisID ]: Converting to UTF-8 ([ text before conversion ])

Text that is converted to UTF-8 is noted.

ERROR(UTF8):       [ osisID ]: Converting to UTF-8 ([ text after first conversion ])

It is an error if after a conversion it still is not UTF-8.

WARNING(UTF8):     osis2mod is not compiled with support for ICU. Ignoring -n flag.

Normalization was requested, but since osis2mod was not compiled for it, it cannot honor the default request.

INFO(V11N):        [ osisID ] is not in the [ v11n ] versification.

Indicates that a verse is not in the versification.

INFO(V11N):        [ osisID ] is not in the [ v11n ] versification. Appending content to [ osisID ]

This like the other indicates a versification problem, but shows where the text will be found. Osis2mod preserves all module content for supported books.

WARNING(V11N): New book is [ name ]  and is not in [ v11n ] versification, ignoring

The name of the book was not recognized as belonging to the chosen versification, it and all of it's content is ignored.

INFO(WRITE):       Appending entry: [ osisID ]: [ text so far ]

If osis2mod encounters text that needs to be appended to a verse that is already in the module. This could indicate that

  • the reference is in the input twice. This typically indicates a problem.
  • more text was found that needs to be added to the prior verse.
  • osis2mod is being run in append mode to fix a verse in the module.
INFO(LINK):        Linking [ osisID ] to [ osisID ]

An osisID such as "Gen.1.1 Gen.1.2 Gen.1.3" was used and the latter are linked to the first.

ERROR(REF):        Invalid osisID/annotateRef: [ invalid attribute value ]

This indicates that the SWORD library was unable to parse the osisID or annotateRef.

FATAL(NESTING):    [ currentOsisID ]: tag expected

This indicates that the specified verse is not balanced with regard to its tags. Building a raw text module, looking in the module for the verse and pairing begin/end tags will help find the problem. Typically, this indicates an end tag that did not have a matching begin tag and all tags before it were properly paired.

FATAL(NESTING):    [ currentOsisID ]: Expected [ topToken.getName() ] found [ tokenName ]

This also indicates that the specified verse is not balanced with regard to its tags. Building a raw text module, looking in the module for the verse and pairing begin/end tags will help find the problem. It could be either a begin or an end tag problem.

WARNING(NESTING):  verse [ currentOsisID ] is not well formed:([ verseDepth ],[ tagDepth ])

This indicates that the verse probably will not show properly in some front-ends in some circumstances. Typically, it shows the problem if the verse is shown in isolation.

ERROR(NESTING):    improper nesting [ currentOsisID ]: matching (sID,eID) not found. Looking at ([ sID ],[ eID ])

OSIS specifies that every sID has a matching eID. Osis2mod is checking that BSP elements are properly nested.

FATAL(COMMENTS): unknown commentstate on comment start: [ comment state ]

This indicates that the comment is not of the form <!-- ... -->.

FATAL(COMMENTS): unknown commentstate on comment end:  [ comment state ]

This indicates that the comment is not of the form <!-- ... -->.

WARNING(PARSE): malformed entity, replacing &[ malformed entity ] with &amp;[ malformed entity ]

This means it found a & that starts an entity but it wasn't terminated by a ; and changed it to something that probably isn't appropriate.

WARNING(PARSE): HEX entity must begin with &x, found [ entity ]

This indicates &X, which is not valid for xml. It is not changed.

WARNING(PARSE): SWORD does not search HEX entities, found [ entity ]
WARNING(PARSE): SWORD does not search numeric entities, found [ entity ]

Since we don't transform HEX or numeric entities to their equivalent UTF-8 value, this will be literal text that cannot be searched.

WARNING(PARSE): XML only supports 5 Character entities &amp;, &lt;, &gt;, &quot; and &apos;, found [ entity ]

XML does not allow character entities. These are passed unchanged to SWORD module. This frustrates search and may only display properly in a front-end using HTML rendering.

WARNING(PARSE): &quot; is unnecessary outside of attribute values. Replace with ".
WARNING(PARSE): &quot; is unnecessary inside single quoted attribute values. Replace with ".
WARNING(PARSE): &quot; is only needed within double quoted attribute values. Considering using single quoted attribute and replacing with ".
WARNING(PARSE): &apos; is only needed within single quoted attribute values. Considering using double quoted attribute and replacing with '.
WARNING(PARSE): &apos; is unnecessary inside double quoted attribute values. Replacing with '.
WARNING(PARSE): &apos; is unnecessary outside of attribute values. Replacing with '.

The &apos; or &quot; was found outside of an attribute value and is being substituted with a straight single apostrophe, ', or double quote, ", respectively.

WARNING(PARSE): While valid for XML, &quot; is only needed within double quoted attribute values.

This warning indicates that the entity is present where it does not need to be.

WARNING(PARSE): While valid for XML, XHTML does not support &apos;.

This warning indicates that the &apos; may not display properly in all front-ends. It was found in an attribute value.

Debug Messages

The following are shown in the same form as the diagnostic messages above. They are given without comment.

-d 1
Output of what is being written to the module. The two osisIDs should always be the same.

DEBUG(WRITE):      [ osisID ]:[ osisID ]: [ text so far ]

-d 4
A stack is maintained to represent the Words of Christ on a per verse basis. This is internal diagnostic of that stack

DEBUG(QUOTE):      [ currentOsisID ]: quote top([ quote stack size ]) [ token ]
DEBUG(QUOTE):      [ currentOsisID ]: quote pop([ quote stack size ]) [ topToken ] -- [ token ]
DEBUG(QUOTE):      [ currentOsisID ]: ([ quote stack size ]) [ topToken ] -- [ token ]

-d 8
Identifies when book and chapter introductions are being determined.

DEBUG(TITLE):      [ currentOsisID ]: OOPS INTRO
        inChapterIntro = [ inChapterIntro ]
        inBookIntro    = [ inBookIntro ]
DEBUG(TITLE):      [ currentOsisID ]: Looking for book introduction
DEBUG(TITLE):      [ currentOsisID ]: Done looking for book introduction
DEBUG(TITLE):      [ currentOsisID ]: BOOK INTRO [ beading ]
DEBUG(TITLE):      [ currentOsisID ]: Looking for chapter introduction
DEBUG(TITLE):      [ currentOsisID ]: Done looking for chapter introduction
DEBUG(TITLE):      [ currentOsisID ]: CHAPTER INTRO [ heading ]

-d 16
Inter-verse material either goes with the prior "verse" or the next. This help diagnose problems related to that split.

DEBUG(INTERVERSE): [ currentOsisID ]: interverse start token [ token ]:[ text ]
DEBUG(INTERVERSE): [ currentOsisID ]: interverse end tag: [ tokenName ]([ tagDepth ],[ chapterDepth ],[ bookDepth ])
DEBUG(INTERVERSE): [ currentOsisID ]: appending interverse end tag: [tokenName ]([ tagDepth ],[ chapterDepth ],[ bookDepth ])

-d 32
The following messages relate to the transformations of containers to milestones.

DEBUG(XFORM):      [ currentOsisID ]: xform empty [ token ]
DEBUG(XFORM):      [ currentOsisID ]: xform push ([ bspTagStack.size() ]) [ token ] (tagname=[ tagName ])
DEBUG(XFORM):      [ currentOsisID ]: xform top([ bsp stack size ]) [ topToken ]
DEBUG(XFORM):      [ currentOsisID ]: xform pop([ bsp stack size ]) [ topToken ]

-d 64
Occasionally a verse reference is outside of the chosen versification. These messages help to understand difficulties that osis2mod has in storing extra-canonical material in the module.

DEBUG(V11N):       [ currentOsisID ] normalizes to [ after ]
DEBUG(V11N):       Chapter max:[ chapterMax ], Verse Max:[ verseMax ]

-d 128
OSIS ids and references can be of a form that SWORD cannot parse. Osis2mod contains a routine that munges these into a form that SWORD can understand.

DEBUG(REF):        Copy range marker: [ marker ]
DEBUG(REF):        Found a work prefix [ workPrefix ]
DEBUG(REF):        Copy osisID:[ osisID ]
DEBUG(REF):        Found a grain suffix [ grain ]
DEBUG(REF):        Found a range
DEBUG(REF):        replacing space with ;. Remaining: [ text ]
DEBUG(REF):        shortended keyVal to`[ text ]`

-d 256
Osis2mod contains two stacks to validate proper nesting of BSP and BCV, respectively. This is an internal representation of the BCV stacks. It provides additional information to understand the diagnostic nesting messages.

DEBUG(STACK):      [ currentOsisID ]: push ([ stack size]) [ tokenName ]
DEBUG(STACK):      [ currentOsisID ]: pop([ tagDepth ]) [ topToken.getName() ]

-d 512
These are general debug messages.

DEBUG(FOUND):        Found first div and pitching prior material: [ text ]
DEBUG(FOUND):        New book is [ currentOsisID ]
DEBUG(FOUND):        Current chapter is [ currentOsisID ] ([ osisID attribute value ])
DEBUG(FOUND):        Entering verse
DEBUG(FOUND):        New current verse is [ currentOsisID ]
DEBUG(FOUND):        osisID/annotateRef is adjusted to: [ simpler osisID or osisRef ]
DEBUG(COMMENTS): in comment
DEBUG(COMMENTS): out of comment

-d 512
The following gives the input arguments.

        path:         [ path ]
        osisDoc:      [ osisDoc ]
        create:       [ append ]
        compressType: [ compType ]
        blockType:    [ iType ]
        cipherKey:    [ cipherKey ]
        normalize:    [ normalize ]

Future Roadmap

List here suggestions for useful enhancements to or improvements for osis2mod.
  • Add a command line flag -x to exclude all OSIS elements with the global attribute editions.[2]
    osis2mod would exclude those elements that match the specified attribute value.


  1. See https://www.sbl-site.org/Fonts/SBLHebrewUserManual1.5x.pdf
  2. The editions attribute is used to specify edition specific content, such as material omitted in Protestant versions of the Bible.

Reporting issues

See also