Quoting Chris Little :
It would greatly encourage use of the bug tracker if there was more
activity. Also, an rss feed might help (I'm not aware of one if there
is one already).
I agree entirely. I think the bugtracker is a great tool for us. (But
it _sorely_ needs an update with respect to ve
I'm getting the same result now.
As Matthew and Ben said, the correct versification needs to be set in
a stand-alone VerseKey. Pretty obvious actually.
Manfred
Am 14.04.2009 um 00:40 schrieb Chris Little:
FWIW, lookup (the cmdline example program called lookup) works fine
on LeningradV11
Quoting Eeli Kaikkonen :
My opinion to the second problem: allow highlighting only when other
features are turned off. I don't see any other reasonable way to do it.
I forgot: my suggestion is based on using the plain text filter of the
engine. It may make the text look different from norma
Hi Matthew ..
Matthew Talbert wrote:
it outputs everything that curl was built with on linux. What you need
to do is modify curl-config it so that it outputs only the following:>
-lcurl -lz
That, together with omitting ICU worked Ok. The resulting library
installed and works OK. I had
Quoting mmital2 :
Hi,
Can anybody suggest what would be the best approach for storing highlighted
words (that is, providing user the capability to highlight certain words of
the chapter or verse using the mouse).Is there any way this information be
stored in module itself? The approach I tried
On Apr 13, 2009, at 4:23 PM, Greg Hellings wrote:
On Mon, Apr 13, 2009 at 3:18 PM, Dmitrijs Ledkovs
wrote:
Hi all!
A few comments about the recent sword tarball. I haven't done any
testing yet, just compiling =D.
A new tool? List-missing gave this:
-./usr/bin/vs2osisreftxt
There files are
On Apr 13, 2009, at 5:31 PM, Chris Little wrote:
Jonathan Marsden wrote:
Matthew Talbert wrote:
I subscribe to sword-svn as an attempt to educate myself on the
library, and, of course, to keep track of current changes. It
would be
a real help to me if the commit messages were longer and mo
On Apr 13, 2009, at 5:57 PM, Manfred Bergmann wrote:
Makes sense.
Now, I've tested a little with the Leningrad module.
No verse text could actually be pulled with my code.
All I get i.e. for "Haggai 1" is:
Haggai 1:1: Neh 2.13
Haggai 1:2: Neh 2.14
Haggai 1:3: Neh 2.15
Haggai 1:4: Neh 2.16
Hagg
On Apr 13, 2009, at 8:58 PM, Jonathan Marsden wrote:
I agree entirely. I think the bugtracker is a great tool for us.
(But it _sorely_ needs an update with respect to versions of Sword
that it recognizes.)
I'd think (hope) that any bugtracker admin can add new product
versions? If not
Hi there,
I have a few commentaries that I've started preparing. They use linked
verses heavily. Two methods are given for linking on the wiki, only one
works.
References like:
annotateRef="Matt.21.1 Matt.21.2 Matt.21.3 Matt.21.4 Matt.21.5 Matt.21.6
Matt.21.7 Matt.21.8 Matt.21.9"
are fine. On
I object (luke-warmly). Cross-references are (in the ESV) tied to the word
in front. If you put a space in, you can't tell which word (before or after)
it is tied to.
Surely this can be fixed in Xiphos? :D
God Bless,
Ben
On Apr 14, 2009, at 9:43 AM, Brian J. Dumont wrote:
Hi there,
I have a few commentaries that I've started preparing. They use
linked
verses heavily. Two methods are given for linking on the wiki, only
one
works.
References like:
annotateRef="Matt.21.1 Matt.21.2 Matt.21.3 Matt.21.4 Matt
I have just released BPBible 0.4.3. A fairly complete list of changes
is at http://www.bpbible.com/news/bpbible-0.4.3-changes, though it is
most likely that I have missed something.
Jon
___
sword-devel mailing list: sword-devel@crosswire.org
http://www
Hi.
There seem to be some serious problems with some of the service.
I can't login to Jira and the forum.
Anyone knows what the problem is?
Manfred
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sw
I just logged in OK to the CrossWire forums. Perhaps it was a server
maintenance slot when you tried.
Currently there are 51 Online Users (50 Guests, 1 Members)
-- David
Manfred Bergmann wrote:
>
> Hi.
>
> There seem to be some serious problems with some of the service.
> I can't login to Jir
We haven't bounced the box for a while, maybe recent package updated
have affected something. I'll cycle things in 15 minutes or so. If
you're on the box now, finish up what you're doing please. "If it
doesn't work, just reboot"-- See what MS has done to my mind.
-Troy.
Manfred B
On Tue, Apr 14, 2009 at 9:48 AM, Ben Morgan wrote:
> I object (luke-warmly). Cross-references are (in the ESV) tied to the word
> in front. If you put a space in, you can't tell which word (before or after)
> it is tied to.
Is there any particular reason that cross-refs in ESV are in front of
wor
Matthew Talbert wrote:
On Tue, Apr 14, 2009 at 9:48 AM, Ben Morgan wrote:
I object (luke-warmly). Cross-references are (in the ESV) tied to the word
in front. If you put a space in, you can't tell which word (before or after)
it is tied to.
Is there any particular reason that cross-re
> This is where Crossway, the publisher, put them.
>
> Note, it might be tied to the following phrase, not the word. So
> programmatically moving them is not a good idea.
I assumed it would be fine, as this is what the RTF filters already
do. In BibleCS, the ESV cross-refs are one space away from
Matthew Talbert wrote:
This is where Crossway, the publisher, put them.
Note, it might be tied to the following phrase, not the word. So
programmatically moving them is not a good idea.
I assumed it would be fine, as this is what the RTF filters already
do. In BibleCS, the ESV cross-refs
20 matches
Mail list logo
