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.x
On 2016-04-14, 22:44 GMT, Emet wrote:
> How to contact with with the xulsword developer, John Austin, on Github?
It is sneaky: look at the top of
https://github.com/JohnAustinDev/xulsword/commit/c43a5a7fb3e5d8341aaeba6150c5a8e1bfc0bfcc.patch
Best,
Matěj
--
https://matej.ceplovi.cz/blog/, Jabb
How to contact with with the xulsword developer, John Austin, on Github?
--
View this message in context:
http://sword-dev.350566.n4.nabble.com/OSIS-Dictionary-module-tp2306425p4656264.html
Sent from the SWORD Dev mailing list archive at Nabble.com.
__
Dictionaries in TEI differently work in different programs, at different
platforms, especially it concerns links to the dictionary and from the
dictionary... I want to create the dictionary in OSIS because OSIS is
supported better, all programs... in a repository there are some
dictionaries in an O
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 Austi
