[sword-devel] OSIS Dictionary module
gpl.programs.info at gmail.com
Thu May 5 01:34:46 MST 2016
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
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
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).
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
> All the dictionary modules available in the IBT repository were made from
> 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,
> 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
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel