Difference between revisions of "User:David Haslam"
David Haslam (talk | contribs) (→Preprocessing tools: OSIS XML) |
David Haslam (talk | contribs) (→Preprocessing tools: inserted new section before this (=== Integrate JSword into Go Bible Creator ===)) |
||
Line 28: | Line 28: | ||
# Construct a SVN directory for managing Go Bible User Interface (UI) translations. | # Construct a SVN directory for managing Go Bible User Interface (UI) translations. | ||
# Mirror Jolon's Go Bible website on the CrossWire server (we have his permission) | # Mirror Jolon's Go Bible website on the CrossWire server (we have his permission) | ||
+ | |||
+ | === Integrate JSword into Go Bible Creator === | ||
+ | With Java SE being the environment in which both programs run, the following idea is worth considering: | ||
+ | |||
+ | * Enhance Go Bible Creator to be capable of processing SWORD modules directly, making use of the [http://www.crosswire.org/jsword/ JSword] API to extract the Biblical text | ||
+ | |||
=== Preprocessing tools === | === Preprocessing tools === |
Revision as of 08:23, 16 June 2009
David Haslam participates in the SWORD Dev mailing list, and is active in developing Go Bible modules for Java ME enabled mobile phones. The sidebar of the Go Bible Team blog lists several more relevant links. I am an experienced Wikipedian.
Contents
Collaboration between CrossWire and Go Bible
In July 2008, I was asked to lead a new CrossWire project to facilitate closer collaboration between CrossWire and Go Bible volunteers, in effect to enable the Go Bible application to act as something like a FrontEnd for CrossWire Bible modules on the Java ME platform. The author of the Go Bible application and the developer kit Go Bible Creator has given this proposal his blessing. The source code for both was already made available as open source.
My contacts at Wycliffe Bible Translators have indicated that this would be of considerable interest to them, as they are keen to make use of the mobile phone technology to publish their translations. Some of them have expressed the opinion that the User Interface of Go Bible is "just right" for reading the Bible on a mobile phone.
While this concept is germinating, I would like to hear from any CrossWire volunteers who would be interesting in participating. I should add that not all participants would need to be Java programmers. There is much to be done towards automating the software tools to convert CrossWire Bible modules to one of the formats suitable for use with Go Bible Creator. So if you are interested, please leave a message in my Talk page.
The are now some pages under construction at [1]. Please help to improve them especially now there is a link from the CrossWire main page.
Tasks list
CrossWire/GoBible
These are some of the tasks for CrossWire to fully adopt Go Bible. Feel free to comment on these in my talk page.
- Transfer source code from Google code – done 2009-02-28 (thanks to scribe)[2]
- Provide screenshots to adorn the web-page
- Update web-pages under construction
- Add link from SWORD Project page header
- Create new CrossWire project for Go Bible
- Define requirements for new development tools
- Investigate software issues listed in Google code
- Setup for GoBible software bug tracking on CrossWire server
- Review items listed in GoBibleRoadmap
- Construct a SVN directory for managing Go Bible User Interface (UI) translations.
- Mirror Jolon's Go Bible website on the CrossWire server (we have his permission)
Integrate JSword into Go Bible Creator
With Java SE being the environment in which both programs run, the following idea is worth considering:
- Enhance Go Bible Creator to be capable of processing SWORD modules directly, making use of the JSword API to extract the Biblical text
Preprocessing tools
For Go Bible Creator, there is a USFM Preprocessor program being developed for Windows. This is not hosted on the CrossWire SVN server. See below for further details.
- Go Bible Creator USFM Preprocessor – This is a tool to parse through and identify, correct and publish USFM file formats into a file format that can easily be put into the Go Bible mobile phone program.
For "milestoned" form of OSIS XML files, there is an XSLT script available to convert these to the "containered" form, which is the form required by Go Bible Creator. Details to be added later.
Miscellaneous
- How to convert a SWORD module to Go Bible. See [3].