[sword-devel] Open Scriptures in relation to CrossWire (was Re: How to help Open Scriptures website development)

Daniel Glassey dglassey at gmail.com
Thu Jan 21 12:30:01 MST 2010

> On 1/21/2010 1:00 PM, Robert Hunt wrote:
>> Yes, I'm most interested in creation of openly-licensed, open-standards
>> formatted, original-language Scriptures, i.e., starting with the basics. (If
>> suitable licensed data is available somewhere else, we might simply have to
>> reformat it.) In other words, I'm wanting to focus on good foundations that
>> many other things can eventually be built on.
>> The web application stuff is secondary for me -- hopefully a whole range
>> of different applications will arise once useful data is available. So
>> perhaps I have different interests than the original OpenScriptures
>> founders?
>> I think this is different from the SWORD project, which seems to focus on
>> modern-language translations???

On Thu, Jan 21, 2010 at 7:26 PM, Daniel Owens <dhowens at pmbx.net> wrote:
> Robert,
> I am totally with you, but you should think about SWORD a bit more,
> especially if providing content offline is your interest.
> SWORD is more about a means of delivery of content and does not create
> content. I think the perceived emphasis on modern-language translations is
> because their repository has so many modern language translations in so many
> languages (this repository has grown by leaps and bounds in the last couple
> of years with non-western translations--really amazing). However, the basics
> are there for original language texts (and even some ancient translations,
> including the LXX and the Vulgate), though I think support for searches and
> for lexical keys that are not ASCII could be improved. What excites me is
> the potential to take open data from OpenScriptures and bring it into SWORD
> in ways that can serve non-English readers. There's nothing that says Greek,
> Hebrew, and Aramaic lexica can't be created in other languages for use by
> pastors, theologians and Bible translators worldwide. SWORD would support
> that quite well if the data were there....

Indeed, and iirc there has been some work on parchment fragment tools
but that may have been something else Troy has been involved in.


More information about the sword-devel mailing list