Create a Bible for TheWord
Find a new module not listed on my site? send me (email@example.com ) a copy or the URL
Stacks & Shelves;
How to Create a Book Module
See Costas' spec documentation file here: http://download.theword.gr/bin/get.php/Formatting_tags_recognized_by_TW3.doc
These are the extensions for Bible files, and the number of lines (which are Scripture text lines, more can be added at the end).
TheWord uses a simple text file for its Bibles. The basic setup of these files are that they are single lines, one for each verse, starting at either Genesis 1:1, or Matthew 1:1, and you count each line/paragraph/hard return as a new verse. Let's look at one as an example.
(This image is from a simple text editor program TOTAL COMMANDER.)
This is Revelation (King James Version). Each verse is on a separate line. Notice that the file will accept some formatting codes <FI> italic text<Fi>, as well as in verse cross references, although that is not recommended. It is better to make a cross reference user file (as per the TheWord manual) and have it available for any Bible Version.
This is all there is to creating a Bible module in THEWORD. There is one extra set of special information at the end of this file.
The following html tags (with no semantic info) can be recognized):
Use of html tags is heavily DISCOURAGED since they bring no semantic info.
<color>: either a string (e.g. red, blue, etc) or in the form #xxyyzz (html format). Also one of the default TW colors can be used with the notation defclrX where X is:
For example: <font color=defclr5>…</font> can be used if you want the color of the footnotes to be used. (since version 2 is using an html renderer, more html tags are supported, but ver.3 will use an rtf renderer with support for these only)
The following semantically recognized tags are supported:
<FI>…<Fi>: for “added” words (usually shown in italics, words added by translator)
<CL>: for new line
<CM>: for new paragraph. NOTICE for CL and CM tags: there must be AT LEAST one CL or CM tag at the end of one verse for other CL/CM tags that are inline to work properly. If (for any reason) the entire .ont file has CL/CM tags only inline the verses (and none at the end of at least one verse), they will not work. I consider this to be totally improbably, but it is something to be aware of.
<FO>…<Fo>: for Old Testament quotes
<FR>…<Fr>: for Words of Jesus (usually rendered in red color)
<FU>…<Fu>: for underline words (no semantic here yet)
<TSn>…<Ts>: for chapter headings. 3 levels are supported (TS1 which is equivalent to TS, TS2, TS3). This text appears as chapter headings. Chapter headings can be exchanged with other modules. They are supported in the beginning of a verse and in the middle. No other formatting tags should be added for the chapter headings itself
<WGXXX[xs]>: Greek strongs codes: they must follow the word they refer to. XXX is the strong’s number
<WHXXX[xs]>: Hebrew strongs
Some notes on strong tags: notice that after the strong number a ‘x’ or an ‘s’ may appear (e.g. <WG123x> or <WG123s>). These 2 letters has special meanings:
<WTXXX>: Morphology codes: corresponds to Robinson’s Morphological codes
<RF>…<Rf>: footnotes: they can appear anywhere in a verse. No formatting tags for text of footnotes
<RX b.c.v-v [q=<quote>]> (or <Rx>): cross-references. The book/chapter/verse index follows. They can appear anywhere in a verse. A range can be defined either using a dash (‘-‘) or a plus sign (‘+’). Dash denote ending verse, plus denotes interval. For example:
<RX 1.1.1> refers to Gen. 1:1
<RX 1.1.3-4> refers to Gen. 1:3-4
<RX 1.1.3+1> refers to Gen 1:3-4
The q attribute is optional and can be used to denote the quote character, e.g.
<RX 1.1.1 q=a>
<RX 1.1.3-4 q=b>
If the q attribute is present, then instead of the usual numbers for the xrefs (1, 2, 3) the quote characters will appear instead (a, b, etc)
<a href=”url”>….</a>: general type links: the url can contain the following (complete this):
(pattern compiled: 'tw://((bible|cmt|dct|bk|book|map|media)\.)?([^#\?]+)(\?)?([^#]*)(#)?(.*?)')
[strong]: for current strong module
[morph]: for current morph module
The following can be added:
_IGNORE_: to denote this as non-Bible text
_NOLINK_: to avoid a link
popup=[0,1,2]: to specify if content should appear in popup when mouse hovers
t=<topic_id>: the topic-id of the module it refers to.
(Give many examples here)
non-Bible text (ver. 126.96.36.1991+). This tag is used to mark some text in
the verse as NOT belonging to the Bible (like notes). This is very
useful when you create custom links inline the text and you don’t want
the linked text (e.g. a number) to be ‘counted’ as Bible text.
usage of NB with a verse rule:
This allows tags in the form: <N 1> in the text that are displayed as foonotes and link to a commentary. Notice the _IGNORE_ directive within the href. Notice also the [vref] that is parsed in the verse rule.
Here are the following information fields at the end of a Bible file from the spec documentation file:
short.title= (abbreviation of the Bible version)
description= (what appears in the tooltip when you mouseover the Bible tab)
about=(what is in the about box when you click on that in the context menu)
version.major=<number> Major version of the module
version.minor=<number> Minor version of the module
requires=a.b.c.d (e.g. 188.8.131.522): minimum program version required to display this module properly
Searching of the text between these 2 chars
User highlighting (it will be offsetted to the right).
OK, since this is a very rare attribute to use and ONLY for texts with special font (only Slavonic as of this writing), I hope it doesn’t limit the functionality too much.
There are some options to importing Bible in the TWImporter program.
visits since July 14, 2009