This document describes the source file markup used in the Erasmus Project.
There are two types of markup: directives and tags. Directives begin with a pound sign (#) at
the start of the line. No white space is allowed before a directive or else it will be treated
as text. Be careful that no lines inadvertantly start with a pound sign unless that line is a
directive. Only one directive is allowed per line.
Tags are either a subset of standard HTML tags, or erasmus-specific tags enclosed in angle
brackets (< and >) that can appear within the text. Name and ID directives are required to
appear before any text or any key directives (such as BCV and TOPIC). Not all HTML tags
are allowed, and not all tag attributes are allowed for those tags. The tags that are allowed
in Erasmus Project sources (and the valid attributes) are described herein.
Keys
A key indicates a type of data - for example, topics and verses indicate two different types of
data. This is like a database key, which allows data to be associated with some means of looking
it up.
There are two types of keys used in markup: primary, and reference.
Primary keys are those to
which a reference work can be opened directly. For instance, in a Bible app, if you enter a book/chapter/verse,
you are providing a primary key and you will be taken to that location in the Bible.
Reference keys are those which refer to a key
within text but are only used indirectly. Reference keys are typically used by clicking on
them within text in the app.
For example, Genesis 1:1 is a primary key in a Bible, which is about creation. The text could include
a topic key reference to "creation", which is different than the verse key. A primary topic key would be
used for an encyclopedia article, but you wouldn't use a primary topic key in Bible text.
Unless otherwise stated, keys defined by directives (such as #BCV or #STRONGS) are primary keys,
whereas key defined by tags (such as <strongs>) are reference keys. Note that when using key references,
one should enclose any surrounding punctuation within the tags. The reason for this is that it provides a
larger target area for users to tap on small screens. If there are two key references in a row, the non-word
characters between them should usually be evenly split, or should favor the smaller reference, for the same
reasons. However, outside of whitespace and punctuation, key references should not include anything other
than the reference text itself. Example of user-friendly reference key usage:
(compare <bcv=Gen 1:27>Genesis 1:27,</bvc><bcv=Gen 2:7> 2:7).</bcv>
Note that the space separating the references is included with the second, smaller, reference - along with the closing
punctuation. We leave the trailing comma with the first reference since it is right next to the first reference and
probably would frustrate the user if they tapped the first reference and were off by a pixel. The smaller the reference, the
more useful is extra horizontal space as a tap/click target.
Directives
Directives must be on a line by themselves, and start with the pound sign (#). There must be no whitespace before this sign.
Directives will automatically end a paragraph. Therefore, placing a directive in the middle of a paragraph will split it into two different paragraphs.
#AUDIO
Optional
Format:
#AUDIO:filename
This directive includes an audio file. Supported file types are midi and mp3. This filename
is the same name referenced in a tag (see below). This directive is typically
followed by one or more meta-data tags. The supported tags are as follows (other tags may be used, but they are ignored):
Tag
Meaning
Title
Recommended. The title of the tune
Author
The author of the tune
Year
The year the tune was written or published
Type
Required. Must be "mid" or "mp3". Indicates if the tune is a midi or mp3.
Meter
The meter of the tune.
Example:
#AUDIO:C:\music\Eventide.mid
<title>Eventide</title>
<author>William H. Monk</author>
<year>1861</year>
<type=mid>
<meter=10.10.10.10>
#AUTHOR
Optional
Format:
#AUTHOR: name
This indicates the author of the reference work. The name should be in the form: lastname, firstname.
Example:
#AUTHOR: Spurgeon, Charles
#AUTOPARAGRAPH
Optional
Format:
#AUTOPARAGRAPH
This indicates that lines are to be gathered together into paragraphs, with blank lines indicating the end of a paragraph. Otherwise, each non-blank line is treated as a separate paragraph. A directive will also end a paragraph.
#BCV
Optional
Format:
#BCV: book chapter:verse
Defines the start of a Bible verse. The next text to follow will be associated with this verse.
Example:
#BCV: Mark 1:1
#BIBLOS
Optional
Format:
#BIBLOS
Indicates that text marked as Greek with directives or tags, uses the Biblos font rather than unicode.
Example:
#BIBLOS
#CATEGORY
Required
Format:
#CATEGORY: cat
Defines what the category of the reference work is.
Valid categories:
Menumonic
Meaning
Bible
A Bible translation.
Book
A book not matching one of the other categories. Organized by outline.
Commentary
A commentary on the Bible.
Lexicon
A language lexicon.
Maps
A pictorial atlas or other work.
Otherbcv
A reference work organized by Bible verse, but not a Bible or Commentary.
Topical
A reference work oriented by topics.
#CONVERT_TRANSLITERATION
Optional
Format:
#CONVERT_TRANSLITERATION
For works containing transliterated Hebrew using upper ASCII characters, this tag
indicates that such text should be converted to UTF8 equivalent characters.
Example:
#CONVERT_TRANSLITERATION
#DEVOTIONAL
Optional
Format:
#DEVOTIONAL: mask
Indicates that this reference work qualifies as a "devotional". The mask indicates how to translate the current date/time to an outline key in the reference work. Each terminal node in the outline is a separate devotion.
Masks can be up to 16 characters long, consisting of one or more of the following fields. When the devotional is opened in the app, each field is replaced by a value corresponding to the current date and time and the result is used to position to an outline with that value.
Field
Meaning
AM
Substitute "AM" if before noon, and "PM" after noon.
D
Current day of the month (eg 5)
MMM
Substitute current all-caps month (eg JANUARY)
Mmm
Substitute current init-capped month (eg January)
R
If used, this should be the only field used. It indicates to choose a random devotion.
Defines a set of footnotes with a common appearance. "id" is the numeric footnote set ID. The first one should be 1, the second should be 2, etc. "type" denotes the appearance of the footnote indicators. The following are valid type values:
Type indicator
Meaning
loweralpha
Indicators are a-z
mixedalpha
Indicators are a-z and A-Z
upperalpha
Indicators are A-Z
The indicators start with the given symbol, and repeats when the end of the sequence is reached. loweralpha and upperalpha sequences repeat every 26 footnotes, and mixedalpha repeats every 52 footnotes.
Example:
#FOOTNOTES:1=loweralpha
See also: <footnote> tag
#ID
Required
Format:
#ID:id
Indicates a unique numeric ID for this reference work. This value is assigned by the Erasmus Project.
Example:
#ID:12
#IMAGE
Optional
Format:
#IMAGE:filename
This directive includes an image file. Supported file types are jpeg. This filename
is the same name referenced in a tag (see below). The directive is typically
followed by meta data tags indicating the image title, scale, etc.
Example:
#IMAGE:c:\images\image1.jpg
<title>Egyptian Empire, 1450 B.C.</title>
<s>mile=0.88</s>
#INTERNAL
Optional
Format:
#INTERNAL
This directive indicates that this work contains data not intended for humans to read.
For instance, it could indicate a database of information for progammatic use.
Example:
#INTERNAL
#LANGUAGE
Optional
Format:
#LANGUAGE:language
Defines the default (primary) language for this reference work. The default language is "English". For reference works with multiple languages, choose the most common one, or the one considered to be the primary language. Note that each language also has a corresponding tag that can be used to change the language within a paragraph. The following are valid languages:
Value
Meaning
Anglosaxon
Anglosaxon
Arabic
Arabic
Aramaic
Aramaic
Belgic
Belgic
Coptic
Coptic
Danish
Danish
Dutch
Dutch
English
English
Ethiopic
Ethiopic
French
French
German
German
Gothic
Gothic
Greek
Koine Greek
Hebrew
Hebrew
Icelandic
Icelandic
Irish
Irish
Italian
Italian
Latin
Latin
Maltese
Maltese
Persian
Persian
Portuguese
Portuguese
Samaritan
Samaritan
Saxon
Saxon
Scottish
Scottish
Spanish
Spanish
Transarabic
Transliterated Arabic
Transaramaic
Transliterated Aramaic
Transchaldee
Transliterated Chaldee
Transethiopic
Transliterated Ethiopic
Transgreek
Transliterated Greek
Transhebrew
Transliterated Hebrew
Transpersian
Transliterated Persian
Transsanscrit
Transliterated Sanscrit
Transsyriac
Transliterated Syriac
Teutonic
Any/all of the Teutonic languages not otherwise listed here
Welsh
Welsh
Example:
#LANGUAGE:Hebrew
#NOSEARCH
Optional
Format:
#NOSEARCH
Indicates that no search index should be generated for this work. Usually used with
internal reference works (see above).
Example:
#NOSEARCH
#NOTOPIC
Optional
Format:
#NOTOPIC
Indicates that the current text has no topical relation. It effectively disables any
preceding #TOPIC directives as if there were no preceding #TOPIC directives.
Example:
#NOTOPIC
#OUTLINE
Optional
Format:
#OUTLINE: level,text
Defines a new outline node or level. The outermost level is 1, the next inner level is 2, and so on. The text is what is shown in an outline in the app. The level specified should be the same level, a lower level, or one level higher than the last #OUTLINE directive's level.
Example:
#OUTLINE:1,Preface
Preface text
#OUTLINE:1,Chapter 1
#OUTLINE:2,Introduction
Introduction to chapter 1.
#OUTLINE:2,Conclusion
Conclusions to chapter 1
#OUTLINE:3:Epilog
Epilog text
#OUTLINE:1,Chapter 2
Chapter 2 text
#OUTLINE:1,Appendix
Appendix text
The foregoing would result in an outline resembling this in the app:
Preface
Chapter 1
Introduction
Conclusion
Epilog
Chapter 2
Appendix
#REM
Optional
Format:
#REM:text
This directive indicates a remark. It is not part of the actual text, but a note by the person processing the data.
#SHORT
Required
Format:
#SHORT: name
Indicates an abbreviated name for this reference work. This must be unique from all other reference works, however it may match the full title.
Example:
#SHORT:KJV
#STRONGS
Required
Format:
#STRONGS:sn
Indicates an article on a Strong's number.
Example:
#STRONGS:g205
#TITLE
Required
Format:
#TITLE:name
Indicates the full title for this reference work. This must be unique from all other reference works, however it may match the short name.
Example:
#TITLE:King James Version
#TOPIC
Optional
Format:
#TOPIC:name
Indicates that the following text is associated with the topic specified by "name".
Example:
#TOPIC:Salvation
#UTF8
Optional
Format:
#UTF8
Indicates that the file is encoded as Unicode UTF8 format. Used if the file does not
begin with a BOM (Byte Order Mark) indication.
Example:
#UTF8
#VERSEMAP
Optional
Format:
#VERSEMAP
Indicates that the following text, up to the next directive, is a list of verse mapping
specifications. This is used in cases where the Bible/manuscript uses a versification
that differs from the "universal" chapter/verse scheme (ie that used in the KJV and most
other modern Bibles). Each line provides one mapping and has the format:
local=universal
where "local" is the chapter/verse used in this work and "universal" is how that verse
corresponds to the "universal" (KJV) chapter/verse. Note that in some cases part of a
local verse may correspond to one universal verse while another part corresponds to a different
universal verse. In these cases, the mapping is always for the correspondance at the start
of the local verse.
Example:
#VERSEMAP
Gen 32:10=Gen 32:9
Gen 32:11=Gen 32:10
#WORD
Optional
Format:
#WORD:language:text
Used in word databases. Indicates that the following text is a definition of a word.
"language" is the language of the word and "text" is the word being defined.
Example:
#WORD:English:Acquire
#WORD_MAPPING
Optional
Format:
#WORD_MAPPING
This directive begins the word map section. Each line in the section has the format:
alternate=word
where "alternate" is an alternate spelling of a word and "word" is the word that the alternate
maps to. This indicates that each occurance of the alternate word should be interpreted as if
it had a <word> tag that maps it to the specified word. This is used to handle alternate
spellings for archaic words. Note that the specified words (both original and mapped) should
be normalized to all lowercase with no whitespace, apostrophes, or punctuation. This cannot be
used to map from one word to multiple words, or from multiple words to a single word.
In this example, if the word "advauntage" is encountered, it is to be treated as equivalent
to:
<word=advantage>advauntage</word>
#WORDDATABASE
Optional
Format:
#WORDDATABASE:language
Indicates that the file is a word database for the specified language.
Example:
#WORDDATABASE:Greek
Tags
This section describes the HTML and erasmus-specific tags that can be embedded in text in an
Erasmus Project source file. Some tags affect the display of text while others provide guidance
for the software. Note that tags only apply to the text until another tag ends them or the
end of the paragraph containing the tag. For instance, a language tag will change the
language from the language specified by the last language tag. No tags will persist into the next
paragraph.
<aramaic>
Format:
<aramaic>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as Aramaic.
<audio>
Format:
<audio:filename>
This tag includes an audio file at this point in the work. Some indicator should be
provided by the software. The file must have been previously defined with the #AUDIO
directive.
<author>, </author>
Format:
<author=name>/author>
Audio meta-data.
This tag indicates the name of the author of a song or piece of audio.
<b>, </b>
Text between these tags is bolded.
Example:
This is <b>important</b>
Would show as:
This is important
<bc>, </bc>
Format:
<bc=book chapter>
Text between these tags is marked as a Bible book/chapter reference. When clicked on in the app, the
specified verse will be opened.
Example:
This sermon is found in <bc=Matthew 5>chapter 5</bc>
<bcv>, </bcv>
Format:
<bcv=book chapter:verse>
Text between these tags is marked as a Bible book/chapter/verse (or verse range) reference. When clicked on in the app, the specified verse will be opened.
Example:
See also <bcv=Matthew 5:6-10>verses 6 through 10</bcv>
<belgic>
Format:
<belgic>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as Belgic.
<big>, </big>
Format:
<big>
Text between these tags is made twice as large as the text around it.
Example:
Thus said the <big>Lord</big>
Would show as:
Thus said the Lord
<block>, </block>
Text between these tags is analogous to being between <div style="float:left;"> and </div>. It is used primarily for displaying blocks of text across the screen. Note that the block is treated as a if it is a paragraph on its own. That is,
any textual changes made inside the block are discarded at the end of the block, including font, colors, direction, <span> and <div> tags, etc. The initial state of the block will be equivalent to the font, foreground color, background color, and current language of the paragraph containing the block, at the point where the block is encountered. However, note that the effect of any langauge in the block tags will persist after the end of the block. The end of a paragraph containing blocks serves as an implicit <div style="clear:both;"> and </div>
<blockquote>, </blockquote>
Text between these tags is indented on the left and right from the surrounding text. There is an implied <br> with both tags.
Example:
As the song says,<blockquote>Jesus loves me, this I know</blockquote>
Would show as:
As the song says,
Jesus loves me, this I know
<br>
This ends the current line and begins a new one.
Example:
A mighty fortress is our God,<br>a bulwark never failing.
Would show as:
A mighty fortress is our God
a bulwark never failing.
<chaldee>
Format:
<chaldee>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as Chaldee,
<coptic>
Format:
<coptic>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as Coptic.
<danish>
Format:
<danish>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as danish.
<div>, </div>
This marks a division of text used as a block of text.
Its purpose is for
use in works like interlinears where independant blocks of text are displayed
across the screen. The <block> tag should be used in place of this
tag in almost all cases.
Example:
<div>Line 1 Line 2</div>
Would show as:
Line 1
Line 2
<english>
Indicates that the following text is to be indexed as English words.
Example:
<english>This is English text
<ethiopic>
Format:
<ethiopic>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as Ethiopic,
<fn>, </fn>
Format:
<fn=index>
Marks the text between these tags as a footnote indicator that references footnote number index. Normally, these tags are generated by use of the <footnote> tag, however this can be used to manually control what indicator is used, and reference an already defined footnote. See the <footnote> tag for more information.
Example:
<sup><fn=2>q</fn></sup>
<font>, </font>
Format:
<font attributes>
Defines the characteristics of text appearing between the tags. The following attributes are valid.
Attribute
Example
Description
face
face="courier"
Use the specified font.
size
size="24"
Set the font size to the specified size. The size can also be relative by preceding with a plus or minus to make it larger or smaller than the previous font size.
color
color="blue"
Set the font foreground color. A valid HTML color must be specified or else an RGB specification of the form: RGB(r,g,b).
<footnote>, </footnote>
Format:
<footnote:set>
The text between the tags is the footnote text to link to this location. "set" is either a footnote set number, or an indicator in quotes.
If "set" indicates a footnote set, the compiler uses it to determine which indicator to use for the footnote and the appropriate superscripted indicator is automatically included at this location in the text.
If "set" is a quoted value, the set is assumed to be footnote set 1, but instead of inserting a footnote indicator that is next in the sequence for footnote set 1, the text between the quotes is used instead. This value is automatically superscripted.
Do not include paragraph tags (<p> or </p>) within the footnote text. Instead, use <br> tags to simulate paragraphing.
Examples:
And he departed and began to proclaim in the decapolis<footnote:1>that is, the Ten Cities</footnote>
When Simon<footnote:"p">that is, Peter</footnote> came, Paul upbraided him
<gothic>
Format:
<gothic>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as Gothic.
<greek>
Format:
<greek>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as greek. See also <transgreek> and #BIBLOS.
<h1>, </h1>
Format:
<h1>text</h1>
Text between the tags is shown as title level 1.
<h2>, </h2>
Format:
<h2>text</h2>
Text between the tags is shown as title level 2.
<h3>, </h3>
Format:
<h3>text</h3>
Text between the tags is shown as title level 3.
<heading>
Format:
<heading>
For use only Bibles. Indicates a heading added to
the Bible text which is not found in the original
text. Not to be confused with implied text (see below).
<hebrew>
Format:
<hebrew>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as hebrew. See also the <transhebrew> tag.
<hr>
Format:
<hr>
A horizontal line is displayed.
Example:
<hr>
<i>, </i>
Format:
<i>text</i>
The text between the tags is italicized.
Example:
<i>emphasize</i>
The text would show up as: emphasize
<icelandic>
Format:
<icelandic>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as Icelandic.
<image>
Format:
<image:filename>
Indicates to include an image file. This filename must have been previously
defined with a #IMAGE directive.
<img>
Format:
<img src="name">
Indicates an image of the specified name.
<imp>
Format:
<imp>
For use only Bibles. Indicates implied text. That
is, text implied by the original language or words
added to make the text more readable to the modern
reader, but not directly correlating to an original
language word.
<irish>
Format:
<irish>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as Irish,
<italic>, </italic>
Format:
<italic>emphasized</italic>
Same as <i>, </i>
<key>
Format:
<key:type=k>
Where "type" is the key type "bcv", "topic", or "strongs"). This tag indicates the start of a key. It operates like a directive, but can be placed inside text.
<latin>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as Latin.
<lemma>, </lemma>
Format:
<lemma=strongsnumber>text</lemma>
Operates exactly as <strongs>, but doesn't create a reference to the number in the index.
<lineimg>
Format:
<lineimg=filename>
Indicates to include an image file. This filename must have been previously
defined with a #IMAGE directive. This differs from the image tag in that the
image is shown with the height adjusted to be the height of the line that the
image is included in. The purpose of this tag is to include tag that is contained
in an image.
<maltese>
Format:
<maltese>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as Maltese,
<meter>
Format:
<meter=text>
Indicates the meter of a song.
Example:
<meter=8.8.8.8>
<p>, </p>
Format:
<p>This is a paragraph</p>
The text between the tags is treated as a paragraph.
<page>
Format:
<page=number>
Indicates the position of a specific page number.
<parsing></parsing>
Format:
<parsing>code</parsing>
The text between the tags is considered as a parsing code.
<r>, </r>
Format:
<r>top,left,bottom,right;text</r>
Image meta data.
Indicates the bounding box of an item in an image, defined
by the top, left, bottom, and right pixels. "text" indicates the
name of the item inside the bounding box. Multiple synonyms can
be specified in the text by delimiting them with semicolons.
This tag can be used to include remarks within text. The tag can contain any text so long as the first three characters are "rem".
Thus, <rem>, <remark>, <remove>, <rememeber>, <rem:this is text>, are all rem tags. It is not part of the actual text, but a note by the person processing the data.
<s>, </s>
Format:
<s>text</s>
Exactly the same as <strike> See also the next item below.
<s>, </s>
Format:
<s>mile=pixels</s>
Image meta data.
When used in an image definition, this indicates the scale of the
image. Primarily used with maps. "pixels" indicate how many pixels
correspond to a mile.
Example:
<s>mile=0.8</s>
<scottish>
Format:
<scottish>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as scottish,
<self>
Format:
<self>
The next reference tag is to be understood as a reference within the current reference work. For instance, a bcv tag
would refer to that key within the current commentary rather than to the default Bible version. It has no meaning if it precedes
a non-reference tag.
<song>
Format:
<song:filename>
Exactly the same as <audio>
<span>, </span>
Format:
<span>text</span>
Indicates a span of text. A style attribute can be used in the tag to indicate a text direction:
<span style="direction:value">
The value can be one of the following:
Value
Meaning
rtl
Right to left
ltr
Left to right
<spanish>
Format:
<spanish>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as spanish,
<strike>, </strike>
Format:
<strike>text</strike>
Text between the tags is shown as strike-through.
Example:
<strike>deleted text</strike>
The example text would show as: deleted text
<strong>, </strong>
Equivalent to <b>, </b>
<strongs>,</strongs>
Format:
<strongs=strongsnumber>text</strongs>
The text between the tags is marked as a Strong's number. When clicked on, the article on the Strong's number is opened.
Equivalent to a <strongs> tag, but when clicked on, information on the strongs number is shown. This is intended for
use on a heading for an article on the strongs number.
<sub>, </sub>
Format:
<sub>text</sub>
The text between the tags is shown as subscripted.
Example:
H<sub>2</sub>O
This text would show as:
H2O
<sup>, </sup>
Format:
<sup>text</sup>
The text between the tags is shown as superscripted.
Example:
Text<sup>2</sup>
This text would show as:
Text2
<table>, </table>
Format:
<table {border="1"}>contents</table>
Indicates text that is a table. The text may contain <TR>, <TH> and
<TD> tags to indicate table layout. The optional "border" attribute can be used to
indicate that you want a border around the table.
Example:
<table>
<tr> <th>Substance</th> <th>Cost/gallon</th> </tr>
<tr> <td>Gasoline</td> <td>$5.25</td> </tr>
<tr> <td>Milk</td> <td>$3.29</td> </tr>
</table>
<td>, </td>
Format:
<tdtd {colspan="count"}>text</td>
The text between the tags is considered a cell of a table. The optional colspan attribute can be used to indicate that
the column spans multiple columns, where 'count' is the number of columns.
Examples:
<td>Column data<td>
<td colspan="2">Two-Column data<td>
<teutonic>
Format:
<teutonic>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as one of the Teutonic
languages. Used when one is unsure of which Teutonic language is being used.
<th>, </th>
Format:
<th th {colspan="count"}>text</th>
The text between the tags is considered a header for a table column. The optional colspan attribute can be used to indicate that
the column spans multiple columns, where 'count' is the number of columns.
Examples:
<th>Column header<th>
<th colspan="2">Two-Column header<th>
<title>
Format:
<title=text>
Image/audio meta data.
Indicates the title of a song or image.
Indicates text that is a topic name. In the second form, the text is linked to the specified topic name. Otherwise the topic name that is linked to is the text between the tags.
The text is marked as a topic name. This is like the <topic> tag, but when clicked, it brings up information rather than a topic article.
This is intended for use on the heading for a topic article.
<tr>, </tr>
Format:
<tr>text</tr>
The text between the tags is considered a row in a table.
<transgreek>
Format:
<transgreek>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as transliterated greek.
<transhebrew>
Format:
<transhebrew>
Text following the tag (up until the next language tag or end of the paragraph) is interpreted as transliterated Hebrew.
<type>
Format:
<type=filetype>
Indicates the type (format) of an audio file.
Example:
<type=mid>
<u>, </u>
Format:
<u>text</u>
The text between the tags is underlined.
Example:
<u>Heading</u>
In this example, the text would look like: Heading
<verse>, </verse>
Format:
<verse=bcv>Text</verse>
The text between the tags is marked as a BCV reference, much like the <bcv> tag, but there will be no reference marked in the index. When clicked on, it will show information on the verse.
This is intended to mark verse indicators within Bible text. Text between these tags is considered not to
be literal Bible text.
Example:
<verse=Gen 1:10>10</word>
<word>, </word>
Format:
<word>=text{:language}</word>
The text between the tags is marked with an alternate word. This is used to disambiguate
certain words. For instance, the archaic "art" could be marked as "are" so that it would
not be confused with the modern meaning of the word "art". It should not be used for archaic
words which are not ambiguous (such as "ye", "thou", etc). If the text in the tag is suffixed with
a colon and a language name, the text is intepreted as a word in the specified language rather than
in the current language for the reference work at that point.
Example:
<word=are>art</word>
<year>, </verse>
Format:
<year=text>
The text indicates the year of a song.
Example:
<year=1875>
Appendix: Languages
Every word of text in a source file has a language associated with it. By default, everything is considered
English. However, the use of the #LANGUAGE directive can change the default language for all text that follows
the directive. When placed at the beginning of the source file, the language applies to all words until/unless another #LANGUAGE directive is encountered. See that directive for a list of valid languages. The language can also be changed within a paragraph by using a language tag, such as >spanish>. All words after the tag will be considered to be that language until another language tag is encounterd, or until the end of the paragraph, when the language will revert back to the default language specified by the last #LANGUAGE directive.
Transliterated languages indicate where a word in another language has been converted (transliterated) into latin characters. This is typically only used for languages that have character glyphs different from latin, such as Greek, Hebrew, and Arabic. Minor differences, such as accented characters and the use of ETH and/or THORN in anglosaxon, do not require transliteration.
The purpose of language tags is not to alter the display of the text (however, see #BIBLOS), but to mark the text for the benefit
of the software using the document. For instance, it can be used to do language-specific searches.