The primary (and officially supported) way to access SWORD modules
from Python is the SWIG wrappers, located in sword/bindings/swig in
the SWORD source. BPBible uses them (afaik), but there should be some
more self-contained examples...
Not finding any good examples, a few years ago I went off, fi
The ESV publishers did all the hard work already to figure out what books
people meant when they used what abbreviations. They can even distinguish
word searches from book references. Their code and data are at
http://www.gnpcb.org/esv/share/about/#bookabbreviations
-Ken
On Sep 19, 2010 11:04 AM,
could have
>> forked the swig bindings, and checked in my changes, then whether or not
>> they became incorporated in the official version, they would be readily
>> available for anyone to find, evaluate and/or fix.
>>
>> Just my $0.02.
>>
>> Thanks,
>>
or new phone works better?
Let me know what you find.
Troy
On 08/24/2010 09:01 PM, Kenneth Arnold wrote:
> I just got an Android phone, and after seeing the...
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailm
I just got an Android phone, and after seeing the state of Bible
software currently available, I'm excited about helping develop a good
SWORD-powered Bible reader for it. I installed Troy's bishop2.apk and
tried to download a module... fail (logcat at end of message). So I
went looking for the code
I just wanted to offer this to the community.
http://github.com/kcarnold/pysword/tree/master
I initially posted about it a while ago (
http://kcarnold.blogspot.com/2008/08/sword-project-bible-reader-in-python.html)
and updated it tonight (
http://kcarnold.blogspot.com/2008/11/sword-project-bible-