I tried to install the new WLC module from the Beta repository. It was
installed in Xiphos. The 1.4 version has normal spaces between the
Hebrew words. But the 1.5 version has no spacing between the words. The
whole sentence becomes one long word. I didn't check the whole module,
just Genesis 1.
Spaces are indeed gone from 1.5. I've got an updated version with this
and a couple of other corrections that I hope to upload tomorrow.
--Chris
Teus Benschop wrote:
I tried to install the new WLC module from the Beta repository. It was
installed in Xiphos. The 1.4 version has normal spaces
Faced with either using a patch I thought was ugly or getting rid of
all the compiler warnings in SWORD 1.6.0, so we can create debug
packages, I made an attempt at the latter option... and it seems to have
worked!
More testing is very definitely needed, but the (sizeable) patch to do
this is at
On Sun, May 24, 2009 at 10:58:52PM -0400, Karl Kleinpaste wrote:
The problem is that curl seems unprepared for the fact that it starts
out in /home/karl when logging in as myself:
This is very common on FTP server. Curl most probably handle this really
well.
CURLFTPTransport: = Send
Thanks for that.
Is the morphology of the Grooves-Wheeler (Westminster) Hebrew database
also included in the WLC module?
Teus.
On Mon, 2009-05-25 at 00:11 -0700, Chris Little wrote:
Spaces are indeed gone from 1.5. I've got an updated version with this
and a couple of other corrections that
No, the morphology is not included, though the morphological
segmentation is. (For example, the first word of Genesis is segmented
into 2 morphemes, a prefixed preposition and a noun.)
--Chris
Teus Benschop wrote:
Thanks for that.
Is the morphology of the Grooves-Wheeler (Westminster)
Is there any front-end that is known to display this morphological
segmentation or do anything with it?
I am asking this because we use the original Scriptures in our Bible
translation projects. And right now we are tied to a commercial program
like BibleWorks.
If the original information that
Hi Teus,
BibleTime does show indicators for the segmentation, depending on the display
style that is chosen (these are customizable to some extent).
If the morph database is copyrighted, an encrypted module would have to be
created for secure distribution. This could even be in the commercial
I copy this request over to Xiphos' mailing list.
A couple of months ago we had a short exchange on the xiphos mailing
list and no one knew what morpheme separation is useful for. So it was
not implemented.
Clearly it is useful for translators. Thanks for clarifying this.
Wrt Morphology tagging
I think that the morphology database is a commercial product. If such a
module would ever become available for the Sword library, and it would
be made available commercially, I would buy a few copies, one for each
of our translators.
Thanks for the hint about BibleTime, will try it out once
Just to be clear: I don't think the WLC in beta will work completely
properly with any existing frontend, as I believe it uses alternate
versification. Until applications support this, the version not in beta will
be better.
God Bless,
Ben
Hello, Teus,
Teus Benschop wrote:
Is there any front-end that is known to display this morphological
segmentation or do anything with it?
The morpheme segmentation is available at:
http://www.tanach.us/Tanach.xml
Choose a passage. Then under Content, you can choose Morphology.
This is a
Hi Troy,
it was indeed - as expected - a problem with my configuration. I used
usrinst.sh to compile and install sword, changed --prefix to /usr/local, but
left --libdir at /usr/lib64, so the old library was not overwritten but still
used. Works nicely now!
Thanks!
mg
Am Sonntag, 24. Mai
Yesterday I installed BPBible 0.4.4 and discovered that the LXXM module in
CrossWire beta caused it to crash. Further investigation revealed that it
also causes an exception in SWORD Project for Windows.
I have therefore reported this in the wiki page.
LXXM is an experimental module (hence its listing in the experimental
section of that wiki page). It employs features (notably VerseTreeKey)
not yet completely implemented in Sword, much less any front end.
There's no expectation that it should work under any front end, in its
posted state.
ANY module in the production repository should work.
The beta repository should be for things that are supposed to work. Issues
found with modules on the beta repository are supposed to be reported.
If we're posting modules that are truly experimental and not content
verification, shouldn't
Mike Hart wrote:
ANY module in the production repository should work.
We're not talking about that.
The beta repository should be for things that are supposed to work. Issues
found with modules on the beta repository are supposed to be reported.
The beta repository is for stuff that is
Hello David,
This is a great resource. Thank you for the pointer.
The Westminster Hebrew Institute has a much newer version of their
database, and it is not publicly available. This is a problem. The
version 4.10 that the Sword WLC module is based on, and this online
source at www.tanach.us, is
18 matches
Mail list logo
