[sword-devel] Explaine ThML markup

[Chris Little]

On Mon, 24 Mar 2003, Victor Zhuromsky wrote:

> Dear Chris,
> could you please, explain to me what tags of ThML to use for making 
> Greek-Russian Lexicon module with (1) Strong's numbers, (2) inside 
> cross-references, (3) Scripture references and (4) font selection for 
> Greek and Hebrew selections.

I would actually recommend using OSIS.  At the moment, it is unsupported 
by Sword, but this will be quickly remedied (as soon as someone un-breaks 
BibleCS).  Once it is, all modules will be converted to OSIS format.  So I 
will answer your questions in terms of both ThML and OSIS:

For ThML: (all documented at http://www.ccel.org/ThML/)
(1) <sync type="Strongs" value="G42" /> marks Strong's Greek lemma 42.
(2) The URI format for ThML is described at 
http://www.ccel.org/ThML/ccel-URI.htm but we do not currently support this 
(and never will).  You may use <a [name|id]="..."> and <a href="..."> 
pairs to link within a single entry, and it will work in those front-ends 
that use HTML for rendering, but you cannot link to other entries and it 
will not work in the Windows front-end.
(3) <scripRef passage="John 3:16">John 3:16</scripRef>  Anything that 
Sword can parse may go into the passage attribute.
(4) Font selection is heavily discouraged and (I hope) not supported.  
Everything should be encoded as UTF-8 and the front-end should be left to 
determine how to assign fonts.  Theoretically, you could use the HTML 
<font> tag.

For OSIS: (documented at http://www.bibletechnologies.net/OSISTools.dsp)
(1) <w lemma="x-Strong:G42">some Greek word</w> achieves the same thing as 
the above <sync> tag in ThML.
(2) Mark targets with osisID attributes and mark <reference> tags with the 
same osisRef value.
(3) <reference osisRef="Bible:John.3.16">John 3:16</reference> achieves 
thesame thing as the above <scripRef> tag, but the value of osisRef must 
be a valid osisRef and the reference itself must follow the book name 
abbreviations described here: 
http://www.bibletechnologieswg.org/osis/specs/BibleBookNames.html .
(4) Discouraged and not possible.  OSIS is entirely semantic, not 
presentational.

--Chris