Could therefore be argued that module creation tools with a GUI interface would also exploit markup features that the API doesn't support at the present so they'd be in the discussion too.
On 14 Jun 2013, at 18:28, Chris Burrell <ch...@burrell.me.uk> wrote: > I think David mentioned the Python script, because currently the Sword engine > doesn't support the full OSIS spec that the Python script outputs. The Python > script produces stuff that the Sword Engine can't parse (presumably?) > > > On 14 June 2013 18:24, Trevor Jenkins <trevor.jenk...@suneidesis.com> wrote: > On 14 Jun 2013, at 18:18, David Haslam <dfh...@googlemail.com> wrote: > > > Better module creation tools (although desirable) are "off topic" for this > > thread. > > > > My question was about what should be in the development roadmap for the > > SWORD engine (API) as new/enhanced features for subsequent releases. > > Except your question that initiated this thread mentioned a Python script not > just the API so it could be taken that any related tool is valid as a > subsequent discussion point. > > Regards, Trevor. > > <>< Re: deemed! > > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page Regards, Trevor. <>< Re: deemed!
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
