[sword-devel] Adding native support for Unified Scripture XML ?

[David Haslam]

The SWORD engine has supported several Bible input file formats over the
years.
The list below is not exhaustive.

1. General Bible Format (GBF)
2. General Import Format (IMP)
3. Theological Markup Language (ThML)
4. Open Scriptures Information Standard (OSIS)

Would it not make SWORD far more congenial to the world-wide Bible
translation fraternity
if we were to add to the SWORD engine native support for what they use as
standard? Namely...

Unified Scripture XML (USX)

USX is closely related to USFM and the ParaTExt software keep these two
formats synchronised.

USX is maintained on github by the United Bible Societies Institute for
Computer Assisted Publishing
See https://github.com/ubsicap/usx

If SWORD became capable to directly handle USX, it would obviate much of the
difficulties
involved in converting USFM to OSIS and fixing all the post-processing
matters.

I know for a fact that one reason YouVersion can so readily publish a new
Bible translation
is because their Bible import officer made the decision several years ago to
support USX.

Streamlining SWORD Bible module publishing direct from USX could be become
just as efficient.
Is this a forlorn hope?

Best regards,

David





--
View this message in context: http://sword-dev.350566.n4.nabble.com/Adding-native-support-for-Unified-Scripture-XML-tp4656602.html
Sent from the SWORD Dev mailing list archive at Nabble.com.