Hi Dali and Edd,
OK - I appreciate your frustration here from both sides!
First of all I just want to assure you Dali that we are working hard to ensure that the next release v2.5 will be much more of an international resource - in that it will be fully Unicode based, from the localised user interface to the database. It is our TOP priority to make ZionWorx a multi-language tool that can be used around the world, without any 'discrimination' against non-English speaking users.
Regarding Bible integration, we want to get this feature in as soon as possible and we want to make sure we do it right. As you say, that means using open standards. We've had an OSIS-based 'engine' working for well over a year now, but we haven't worked anymore on it because the standard doesn't seem to have settled down yet or have been that widely adopted.
As Edd said, the other issue is of course copyright. Granted, that doesn't need to be a massive stumbling block as there are a number of translations (especially non-English) that are freely available in a variety of formats, but it still is a slow and frustrating problem. The decision for us as developers is to decide which 'format' to support and put our effort into, and also how to use a 'plug-in' design so that users can search for/create their own Bible modules as required, which takes the burden of distribution out of our hands...
Thanks very much for the link to the Sword Project - perhaps like Edd, I too assumed this was linked to eSword, which it apparently isn't! Having had a quick look at the website, I see that the core of this is a cross-platform API to aid development of Bible study software. So, from a brief look, this could well be a viable platform for ZionWorx to natively support. I'm going to take a deeper look at what's on offer and how it might fit into our current development environment. Once I've done this I'll reply here with some thoughts on how to move forward.
Thanks everybody for your input...
Christian.