[sword-devel] OSIS Dictionary module

[John Austin]

Hi,
IBT uses osis-converters which currently uses OSIS for dictionary 
markup, even though tei2mod is used to create dictionary modules.

An OSIS file is created for the dictionary using usfm2osis.py. Then 
tei2mod is used to create the SWORD dictionary module, so 
osis-converters runs osis2tei.xsl 
(https://github.com/refdoc/Module-tools/blob/master/bin/osis2tei.xsl) on 
the OSIS file to create a TEI file that has the structure required by 
tei2mod. However the markup within the TEI structure is still OSIS. So 
the TEI file has TEI structure, but uses OSIS the original markup. 
That's why the resulting dictionary modules have within their .conf 
files: SourceType=OSIS.

This is done as a migration step towards TEI, but osis-converters will 
not use any non-OSIS markup in dictionaries until/unless SWORD TEI 
support is complete across front-ends (xulsword already supports TEI 
markup, but other front-ends may not yet).
-john


On 04/14/2016 08:41 PM, David Haslam wrote:
> Dear Anders,
>
> Though I've never made a Dictionary module from OSIS, I know someone who
> has.
>
> All the dictionary modules available in the IBT repository were made from
> OSIS.
> e.g. Modules BURDICT, KHKDICT, TBNDICT, TVNDICT, etc.
>
> I suggest that you make contact with the xulsword developer, John Austin.
>
> xulsword is hosted at https://github.com/JohnAustinDev/xulsword
>
> John also uses this mailing list occasionally.
>
> Best regards,
>
> David
>
>
>
> --
> View this message in context: http://sword-dev.350566.n4.nabble.com/OSIS-Dictionary-module-tp2306425p4656262.html
> Sent from the SWORD Dev mailing list archive at Nabble.com.
>
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page
>