[sword-devel] Re: sword-devel Digest, Vol 24, Issue 46

[Yiguang Hu]

ON CLUCENE
I have a install (websword)
(http://rock.ccim.org:8080/bible) with chinese bibles.
I can try to test it if you can show me how to enable
this (Just the make file change in
bindings/corba/orbitcpp ? or need more changes). 
Thanks
Yiguang

--- sword-devel-request at crosswire.org wrote:

> Send sword-devel mailing list submissions to
> 	sword-devel at crosswire.org
> 
> To subscribe or unsubscribe via the World Wide Web,
> visit
> 
>
http://www.crosswire.org/mailman/listinfo/sword-devel
> or, via email, send a message with subject or body
> 'help' to
> 	sword-devel-request at crosswire.org
> 
> You can reach the person managing the list at
> 	sword-devel-owner at crosswire.org
> 
> When replying, please edit your Subject line so it
> is more specific
> than "Re: Contents of sword-devel digest..."
> 
> 
> Today's Topics:
> 
>    1. Fixes for CLucene 0.9.x (Joachim Ansorg)
>    2. Re: KJV2006 - 4th Beta (Joachim Ansorg)
>    3. BibleCS - possible bug (Barry Drake)
>    4. Re: BibleCS - possible bug (Moses Truong)
> 
> 
>
----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 29 Mar 2006 23:13:00 +0200
> From: Joachim Ansorg
> <nospam+sword-devel at joachim-ansorg.de>
> Subject: [sword-devel] Fixes for CLucene 0.9.x
> To: sword-devel at crosswire.org
> Message-ID:
>
<200603292313.01038.nospam+sword-devel at joachim-ansorg.de>
> Content-Type: text/plain;  charset="us-ascii"
> 
> Hi,
> I just added fixes in svn to compile with CLucene
> 0.9.x (tested with 0.9.10).
> 
> It works fine with 0.9.10, the indexes are huge
> though. This can be tweaked by 
> calling
> 	writer->setUseCompoundFile(true);
> // 1000 or another large number. The higher it is
> the higher 
> // the memory conumption is.
> 	writer->setMinMergeDocs(1000);
> 
> afaik. This is not yet included.
> 0.9.11 will have a fixed optimize(), so these calls
> are probably not required. 
> 0.9.10 has a buggy optimize though (I think).
> 
> 0.9.11 should be released soon.
> 
> I tested the indexing with the KJV, which worked
> fine for me.
> Testing with unicode modules like WLC is not yet
> done. I don't have a unicode 
> enabled client installed which uses the Sword calls.
> 
> Joachim
> -- 
> <>< Re: deemed
> www.bibletime.info
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Thu, 30 Mar 2006 09:07:26 +0200
> From: Joachim Ansorg
> <nospam+sword-devel at joachim-ansorg.de>
> Subject: Re: [sword-devel] KJV2006 - 4th Beta
> To: "SWORD Developers' Collaboration Forum"
> 	<sword-devel at crosswire.org>
> Message-ID:
>
<200603300907.26862.nospam+sword-devel at joachim-ansorg.de>
> Content-Type: text/plain;  charset="iso-8859-1"
> 
> Hi,
> thank you for taking the time to explain these
> things.
> BibleTime 1.6 will (almost) work fine with the new
> KJV2006 module.
> Limitations are in the formatting. As soon as Sword
> switches to verse elements 
> in the text itself it should be easier to work with
> the osis texts.
> 
> Joachim
> 
> > Joachim Ansorg wrote:
> > > Hi,
> > > thank you for your continued work on the KJV
> module.
> > >
> > > I tested beta4 in BibleTime.
> > > I fixes BibleTime to support milestones with
> type x-p. The paragraph
> > > marker is now shown correctly in the text.
> Should that milestone also
> > > start a newline or a new paragraph or just
> insert the marker?
> >
> > In the traditional printing of the KJV, every
> verse begins on a new line.
> > The paragraph mark appears after the verse number.
> >
> > Since our user interfaces can provide a richer
> experience, we can do
> > with it as we please.
> >
> > What I would suggest is that each paragraph start
> on a new line and
> > perhaps have a blank line above it. You may wish
> to surround the
> > paragraph marker with space to make the text more
> readable.
> >
> > I still have to validate the paragraphing as a
> cursory glance shows that
> > we have many more paragraph markers than the 1769
> version had.
> > I will probably preserve them via something that
> should be ignored.
> > (e.g. a different custom milestone.)
> >
> > > Multiple strongs for one word (e.g. created in
> Gen.1.1) are split by
> > > space. I think the old module (other modules?)
> use | as split marker. Is
> > > there any official guideline for the split
> marker?
> >
> > Yes. OSIS does not allow the | in lemma or morph.
> They do allow spaces.
> >
> > > The NT contains the morph prefix robinson. I
> ever thought this should be
> > > used as a module name, at least we do in BT =)
> >
> > We had been using x-Strongs and x-Robinsons, but
> OSIS does not allow these.
> >
> > The prefix is an osis work prefex that is defined
> in the header element
> > of the osisText element. It is not a module name.
> OSIS lets it be
> > anything at all. But since the osis2mod process
> strips out the header
> > element, we have to have a convention. I am using
> strong and robinson at
> > Troy's suggestion.
> >
> > I think the sword engine already recognizes these.
> >
> > > Since it's lower case (the old one was Robinson
> I think) this doesn't
> > > work. What is the right handling of a morph
> prefix? Are there any
> > > official types defined (can't remember if there
> are some in the specs
> > > right now).
> >
> > So far the only ones that have any real value are
> strongs and robinson.
> > There is strongsMorph, but Chris is working on a
> module to replace that.
> > When he gets it done, we may change the prefix to
> something more
> > constructive, maybe "chris" ;)
> >
> > > Thank you for you help and work,
> > > Joachim
> > >
> > >> L.Allan-pbio wrote:
> > >>> Thanks for working on this.
> > >>>
> > >>> I would add a vote for providing KjvLite (with
> all or most of the
> > >>> embedded tags removed.)
> > >>
> > >> Here you go:
>
http://www.crosswire.org/~dmsmith/kjv2006/kjvlite.zip
> (If
> > >> it is not there, check back later)
> > >>
> > >> I created it by running the following xsl. I
> left divineName,
> > >> transChange, notes and q.
> > >>
> > >> If you don't want these, it is a trivial change
> from match="osis:w" to
> > >> match="osis:w|osis:q" (or what ever you don't
> want.)
> > >>
> 
=== message truncated ===


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com