The first video link was mistyped. It should be
http://thegoan.com/firebible/screencasts
http://thegoan.com/firebible/screencasts
David
Brian Fernandes wrote:
Blog post: http://thegoan.com/blog/firebible-1-1-released/
This version of FireBible was also submitted as an entry to the
Chris Little wrote:
Character escaping was taken into consideration when writing the
osisID/osisRef format. The relevant bit of the regex is:
(\p{L}|\p{N}|_|(\\[^\s]))+
The last option permits escaping any non-space character with a
leading \. Further to that, NBSP (0xA0), by convention,
One of the http://www.crosswire.org/study/ sections reads,
An OSIS editing tool plug-in for Microsoft Word 2003 is under construction.
The tool will be completed in the spring, 2004, and will let you encode
texts in OSIS for use in the tools available on this site.
Please would someone
Just added a note about Ubiqity being supported in
http://www.crosswire.org/wiki/Choosing_a_SWORD_program#Other Other features
not listed otherwise
- David
Brian Fernandes wrote:
I released FireBible about a week ago, but forgot to announce it here:
Blog post:
CrossWire volunteers who are Wikipedians may like to try and bring this page
more up to date.
http://en.wikipedia.org/wiki/The_SWORD_Project
http://en.wikipedia.org/wiki/The_SWORD_Project
It may also be helpful to create new pages for
http://en.wikipedia.org/wiki/Notability_in_Wikipedia
A good place to look for the use and application of text to speech is Vinux
- which originally was based on Ubuntu but because of problems with Ubuntu's
default audio settings has moved over to Debian where just ALSA is used -
and the synthesizer just rocks! Vinux 2.0 has speakup and espeakup,
It may also be helpful to create new pages for
http://en.wikipedia.org/wiki/Notability_in_Wikipedia notable frontends such
as FireBible.
This is probably not such a good idea (or at least a waste of time),
considering that the previous individual articles for GnomeSword (as
it was then), and
Is their someone I can/should send a patch to that fixes the python
swig bindings issues in 1.6/1.6svn.Or do I send it to the mailing list?
Nathan
___
sword-devel mailing list: sword-devel@crosswire.org
I'm working on porting the whole stack to another device that does
not have any of the libraries yet. I will use 21b if I have to to get
past the issue. But I would love to use .23 if possible.
I think it would be great to have support for .23. As far as I know,
no one has worked on
You can send it to the mailing list. The Python bindings are
maintained primarily by the BPBible team, from what I understand, so
you can also get in touch with them for more help on the binding
specifically.
--Greg
On Mon, Oct 19, 2009 at 11:52 AM, Nathan Anderson
nat...@andersonsplace.net
Greg,
Actually the patch is against the Sword library and not the python
bindings. The swig library which generates the bindings (for several
languages) has serious issues with nested classes and a recent change in
Sword linrary added a nested class that basically has broke the ability
Matthew,
Thanks for letting me know -- I kinda wondered if that was the case.
I have already deb-ized the .21b for this device to get something going.
When I have some free time; I will come back and work on understanding what
sword needs from Clucene and will attempt to make a #DEFINE
Thanks for the patch Nathan,
Is this really necessary? This has been in the code for quite some time
and BPBible has been working with swig bindings for quite some time with
this in the code. I don't believe this inner class should ever be
exposed in the bindings, as it is a mechanism we use in
On Tue, Oct 20, 2009 at 8:36 AM, Troy A. Griffitts scr...@crosswire.orgwrote:
Thanks for the patch Nathan,
Is this really necessary? This has been in the code for quite some time
and BPBible has been working with swig bindings for quite some time with
this in the code. I don't believe this
Brian J. Dumont wrote:
Chris,
Thanks very much for the response. So if I understand you correctly, a
proper reference to the module Concord at key:
/The Smalcald Articles/Preface of Dr. Martin Luther
would be written as:
reference
Troy,
Your welcome for the patch. ;-)
Well, I might be the _new_ guy; but I don't typically waste my time
trying to patch something and return it up-stream if it isn't broken. So I
would say yes it is necessary. ;-)
If the class was totally used internally
On Tue, Oct 20, 2009 at 10:02 AM, Nathan Anderson nat...@andersonsplace.net
wrote:
Troy,
Your welcome for the patch. ;-)
Well, I might be the _new_ guy; but I don't typically waste my time
trying to patch something and return it up-stream if it isn't broken. So I
would say
Thanks for your help Chris,
I've got some work ahead of me. BTW, I'll look into whether I should
re-encode the Book of Concord.
Thanks,
Brian
___
sword-devel mailing list: sword-devel@crosswire.org
I am encoding at the moment a Belarussian Bible translation for which
David Haslam acquired permissions.
I am getting stuck on the encoding of Selah.
Marking it correctly up (and as per given text) results in validation
errors as the element l type=Selah expects to be within a larger
poetic lg
Ben,
Ok, you got my attention g totally!
I could not not find any way to compile the Sword.cxx module generated
by swig in 1.60/1.60svn (I could do it fine in 1.5.11) How exactly did you
get past the VerseManager referencing the inner TreeView PositionListener
class in 1.60?
It looks like you need a newer version of SWIG.
God Bless,
Ben
---
Multitudes, multitudes,
in the valley of decision!
For the day of the LORD is near
in the valley of decision.
Giôên 3:14 (ESV)
On
Ben,
So a newer version of Swig will actually parse inner classes? Sweet.
I did try 1.3.40 (I downloaded it an compiled it) but I had a different
issue (CLucene 0.9.23) and decided not to pursue it since I don't think I
can even get a newer version of swig on the build-bots that I have to
On Tue, Oct 20, 2009 at 9:42 AM, Chris Little chris...@crosswire.org wrote:
Ideally, osisRefs should point at references using a standard reference
scheme. Obviously that won't exist for every work, but I suspect there is a
standard reference scheme for the Book of Concord. I find a description
Peter von Kaehne wrote:
I am encoding at the moment a Belarussian Bible translation for which
David Haslam acquired permissions.
I am getting stuck on the encoding of Selah.
Marking it correctly up (and as per given text) results in validation
errors as the element l type=Selah expects to be
24 matches
Mail list logo
