If it is just compatibility issue, then i need to just ifdef it in Mini
code (it been not synced since initial commit in April 2011 indeed).
I did not found such setup for clucene writer in Sword code, so i suppose
that Sword based frontends have more slow index building than it could be,
at leas
And here's the documentation for the method
http://lucenenet.apache.org/docs/2.9.4/html/3b1c494d-9376-8fe5-9582-dd09f22a7584.htm
On Wed, Aug 14, 2013 at 12:20 PM, Jaak Ristioja wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi!
>
> The line was removed in 2011 by commit 3e7c91:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
The line was removed in 2011 by commit 3e7c91:
commit 3e7c91810726ca5632371410f587ee05a3b5364a
Author: Gregory Hellings
Date: Sun Oct 23 13:17:51 2011 -0500
Compatibility with CLucene 2.
Patch adapted from Jonathan Dieter a
Post it here because PocketSword team potentially would be interested too.
Some time ago i got strange issue when indexing time in BibleTime Mini
increased from 9 minutes to several hours. Investigating this i found that
one line been removed from BibleTime code, it have following setup for
clucen
Deji,
That's awesome! Thank you (and to Tom)!
Anyone want to take a shot at adding to configure.am and cmake a define
and ifdef those lines depending on the version of clucene found?
On 10/04/2011 05:46 AM, Deji Akingunola wrote:
On Fri, Sep 2, 2011 at 12:48 PM, Greg Hellings wrote:
So
On Fri, Sep 2, 2011 at 12:48 PM, Greg Hellings wrote:
> So I'm looking at the trouble with building CLucene 2 and the first
> snag seems to hinge around the helper functions we use -
> lucene_utf8towcs and lucene_wcstoutf8 and the like. These are still
> present in CLucene 2, but they are not expo
On 17/09/2011, at 3:07 AM, Peter von Kaehne wrote:
> This was the core argument against making indices distributable and
> downloadable.
I know that this has the potential for some issues, and I have engineered this
into PS so that when we move clucene versions, I can hit a switch and
invalid
16 Sep 2011 11:39:48 -0500
> Von: Greg Hellings
> An: "SWORD Developers\' Collaboration Forum"
> Betreff: [sword-devel] CLucene Compatibility
> While working on updating SWORD (and BibleTime) to handle CLucene
> 2.3.3.4 I have come across statements that clucene-
While working on updating SWORD (and BibleTime) to handle CLucene
2.3.3.4 I have come across statements that clucene-core-0.9.21b is
compatible with Lucene 1.9.1 and clucene-core-2.3.3.4 is compatible
with Lucene 2.3. I asked Troy in IRC if this would mean invalidating
any existing indexes. He be
> It is actually UTF8 to Unicode from everything I've been able to read.
> utf8towcs is, from what I have read, supposed to represent every
> Unicode character as a single wchar_t which is supposed to be wide
> enough to hold the entire Unicode point value in a single space. If
> I'm mistaken and
On Fri, Sep 2, 2011 at 12:22 PM, Matthew Talbert wrote:
>> So I'm looking at the trouble with building CLucene 2 and the first
>> snag seems to hinge around the helper functions we use -
>> lucene_utf8towcs and lucene_wcstoutf8 and the like. These are still
>> present in CLucene 2, but they are no
> So I'm looking at the trouble with building CLucene 2 and the first
> snag seems to hinge around the helper functions we use -
> lucene_utf8towcs and lucene_wcstoutf8 and the like. These are still
> present in CLucene 2, but they are not exposed through a public
> header. As I see it, we can eit
On 09/02/2011 12:48 PM, Greg Hellings wrote:
So I'm looking at the trouble with building CLucene 2 and the first
snag seems to hinge around the helper functions we use -
lucene_utf8towcs and lucene_wcstoutf8 and the like. These are still
present in CLucene 2, but they are not exposed through a pu
So I'm looking at the trouble with building CLucene 2 and the first
snag seems to hinge around the helper functions we use -
lucene_utf8towcs and lucene_wcstoutf8 and the like. These are still
present in CLucene 2, but they are not exposed through a public
header. As I see it, we can either choose
A Xiphos bug report...
https://sourceforge.net/tracker/?func=detail&aid=3291274&group_id=5528&atid=105528
...observes that searching for "[est]" in FreJND, without specifying
regular expression, causes Xiphos to crash.
He's right:
#0 0x003adac74749 in lucene_tcslwr(wchar_t*) () from
/us
btw, "multi-character" is not accurate. It's just too early in the
morning to figure out the correct thing to say.
Matthew
___
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsu
Troy,
I don't think they have any intention of supporting multi-character
UTF-16. I did quite a bit of research on this a while back, most of
which can be found by going back and reading my emails about this. In
the end, UTF-16 with single characters is plenty good enough for the
vast majority of
It looks like the lucene_utf8towcs method we are using from
CLucene/config/utf8.cpp was provided by RedHat and probably had no
intention to work on Windows:
http://www.google.com/codesearch/p?hl=en#7HljlF5wh14/trunk/clucene-core-0.9.21/src/CLucene/config/utf8.cpp&q=lucene_utf8towcs&d=2
We don't n
> 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 able patch to
>>>
llow .23 or .21 to work.
>>>>
>>>> As for indexes, I'm not sure -- I understand .21 is compatible with
>>>> 1.8/9 branch of Jlucene. But .23 is compatible with 2.3.2 branch of
>>>> Jlucene
>>>> and that version of J/C Lucene is muc
Nic Carter wrote:
Thanks for the quick reply, Greg :)
I have CLucene running fine on the iPhone (I found getting cURL a bit
more tricky!), I'm just curious about CLucene .23 (faster, less
memory footprint) vs .21 (which is what sword currently uses) and
Nathan was looking into this, I think?
athan.
-Original Message-
From: Nic Carter [mailto:niccar...@mac.com]
Sent: Wednesday, November 25, 2009 10:44 PM
To: SWORD Developers' Collaboration Forum
Cc: Nathan Anderson
Subject: Re: [sword-devel] Clucene .09.23 and Sword 1.6.0 / 1.6-svn
-Compiling Help
Hi there Nathan.
23 is compatible with 2.3.2 branch of Jlucene
>>> and that version of J/C Lucene is much faster, with if, I recall correctly,
>>> a slightly lower memory footprint. Since the device I'm working with is a
>>> low memory and a embedded arm chip; faster and lower memory re
> low memory and a embedded arm chip; faster and lower memory requirements is
>> a very (very) nice perk. ;-)
>>
>> Nathan.
>>
>> -Original Message-
>> From: Matthew Talbert [mailto:ransom1...@gmail.com]
>> Sent: Monday, October 19, 2009 12:02 PM
>&g
m working with is a
> low memory and a embedded arm chip; faster and lower memory requirements is
> a very (very) nice perk. ;-)
>
> Nathan.
>
> -Original Message-
> From: Matthew Talbert [mailto:ransom1...@gmail.com]
> Sent: Monday, October 19, 2009 12:02 PM
>
To: SWORD Developers' Collaboration Forum
Subject: Re: [sword-devel] Clucene .09.23 and Sword 1.6.0 / 1.6-svn
-Compiling Help
> 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 g
> 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
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.
Nathan
-Original Message-
From: Troy A. Griffitts [mailto:scr...@crosswire.org]
Sent: Sunday, October 18, 2009 11:27 AM
To: SWORD Developers
Dear Nathan,
Could you check to see where both libclucene.so and include/CLucene
lives? The first might be in someplace like:
/usr/lib64/libclucene.so
/usr/lib/libclucene.so
/usr/local/lib64/libclucene.so
/usr/local/lib/libclucene.so
the other should be in /usr/include/CLucene or /usr/local/inc
I'm new to the mailing list, and I scanned the archives back to dec 2008 and
didn't see any solution to this issue. I'm attempting to make the core
components on a linux machine.
I can apparently compile Clucene fine. I can compile ICU fine.
However compiling Sword 1.60 or 1.60-svn I get:
..
I am using the latest version of CLucene, but not the SVN version of
SWORD. I will check out a copy of that and see how that improves
things. I'm still not sure if it would produce tolerable running times
on the iPhone, but it's worth a shot because setting up an index
server would be a sli
Dear Ian,
Are you using the latest version of SWORD from SVN along with its
clucene integration (and the latest version of clucene)? We had done
some work to optimize index creation. It shouldn't take anywhere near 1
minute on a desktop system. We've talked about distributing indexes in
the
Hello all,
I have determined that using CLucene is going to be the fastest way to
do searching with the iPhone frontend. Search times are very fast once
the indexes have been built. The problem that I am facing now is the
time required to index a module. In the simulator, the device
appare
Fellow toilers,
I've been working with the BibleTime progress as they are porting
towards KDE4 and I have been mainly looking at building on the Mac
side of things. Earlier in this process I had run into some linking
errors related to CLucene, cURL and ICU, which the BibleTime
developers attribut
Manfred,
What ever you do, don't index a module without deleting the current
index, if there is one. The code, as it stands, will add data to an
existing index, but not as an update but as a duplication. This will
make the index much bigger than it needs to be and it will provide
multiple
Manfred,
Have a look at the source for sword/utilities/mkfastmod.cpp and
sword/examples/cmdline/search.cpp
Checking whether or not the indecies are created is the most confusing
part. Originally, the plan was to let the SWModule::search method
return whether or not a search was
Troy,
that's great.
I finally compiled sword with clucene support for the Mac.
Unfortunately currently only for PPC platform because cross-compiling
clucene for Intel didn't work. Maybe I need someone with an Intel Mac
for this.
However, there are some question to using the sword clucene
Troy,
The patch seems to be working for me now. Thanks so much!
PierreOn Sat, 2007-05-19 at 14:48 -0700, Troy A. Griffitts wrote:
> Terry,
> Thanks for the patch! Applied. I added a few comments and removed my
> initial comments which questioned why in the world clucene-config.h was
Terry,
Thanks for the patch! Applied. I added a few comments and removed my
initial comments which questioned why in the world clucene-config.h was
being sought in /usr/lib. Thank for the explanation.
Pierre,
Thanks for the report. I added a check for an explicit
--with-cluc
Troy,
here's a new patch
you were right of course :)
terry
On Fri, 2007-05-18 at 21:55 -0400, Terry Biggs wrote:
> Troy,
>
> some of us don't have lib64 :(
> we just have lib and that's where clucene-config.h lives in Ubuntu-7.04
> other than that it worked great.
>
> here's a patch that makes
I'm getting this error in the latest SVN trunk
checking how to include clucene... ./configure: line 20201: cd: yes: No
such file or directory
excluding support
configure: WARNING: Could not detect clucene location. To enable
clucene, you must
call configure with the --with-clucene
Troy,
some of us don't have lib64 :(
we just have lib and that's where clucene-config.h lives in Ubuntu-7.04
other than that it worked great.
here's a patch that makes it go.
terry
On Fri, 2007-05-18 at 15:41 -0700, Troy A. Griffitts wrote:
> OK guys, I had some time today to look into the re
OK guys, I had some time today to look into the reported problems of
compiling sword without clucene. Being a novice, at best, at autotools,
I've committed a delta that I THINK works. If those who have had
troubles could try the latest SVN trunk out and let me know, I'd
appreciate it. Those
Manfred,
I believe Will's reason for not using CLucene in SWORD was because
he couldn't easily get CLucene compiled on the Mac. Using SWORD's
CLucene implementation has many advantages, and I'm not sure any real
world disadvantages. But, of course, I'm biased.
o You get to share indexes
I'll give my 2 cents on index versioning.
We need to tackle the whole question of index versioning. It is
something that I am going through right now with JSword and
inadvertently didn't think about it when I made a change to Sword.
As you noted Java Lucene is ahead of CLucene. Right now it is
Hi,
> When, I don't know. But it's used exactly as in frontends: it's a search
> engine for module texts.
>
> > Can it be used by client applications for searching?
>
> It's integrated into sword API, it's just one of the search engines.
> I have tested it with modified diatheke. I built the index
On Thu, 17 May 2007, Manfred Bergmann wrote:
> Hi.
>
> Since when is CLucene integrated in Sword and for what exactly is it
> used?
When, I don't know. But it's used exactly as in frontends: it's a search
engine for module texts.
> Can it be used by client applications for searching?
It's integ
Hi.
Since when is CLucene integrated in Sword and for what exactly is it
used?
Can it be used by client applications for searching?
I'm not really satisfied with using Java Lucene in Objective-C in
MacSword.
It is possible to use Java classes in Objective-C but it is not very
straight forwa
On Aug 14, 2006, at 2:42 AM, Joachim Ansorg wrote:
> DM,
> thank you for your comments on that topic.
>
> You're right, that updates will break the native CLucene order. But
> since
> updates are not possible in Sword at the moment using CLucene to
> sort the
> results should work fine.
>
> I
DM,
thank you for your comments on that topic.
You're right, that updates will break the native CLucene order. But since
updates are not possible in Sword at the moment using CLucene to sort the
results should work fine.
I can't think of a situation where updates could be used for a module inde
Joachim,
I could be wrong, but I'm not sure that CLucene's sort would product
the right results.
IIRC, we store the OSIS ids and these are what need to be sorted into
Biblical Order.
If it were true that the verses (aka lucene documents) were added in
order then one could use the ordering o
The current clucenen has support for the native order, it just needs to be
patched into sword.
Joachim
> The ListKey container which is returned from SWModule::search has a
> newly added .sort() method.
>
> Eeli Kaikkonen wrote:
> > On Sun, 6 Aug 2006, Eeli Kaikkonen wrote:
> >> I tried to compi
The ListKey container which is returned from SWModule::search has a
newly added .sort() method.
Eeli Kaikkonen wrote:
> On Sun, 6 Aug 2006, Eeli Kaikkonen wrote:
>> I tried to compile Sword for some time ago on Debian unstable. CLucene
>> had some problem then. Now I tried again (after upgrading
On Sun, 6 Aug 2006, Eeli Kaikkonen wrote:
>
> I tried to compile Sword for some time ago on Debian unstable. CLucene
> had some problem then. Now I tried again (after upgrading Debian) and
> compilation worked for some reason, maybe CLucene had been updated.
>
>
> Now the problem is that I don't kn
Hi,
it seems to work fine on Debian witl libclucene0 and libclucene-dev (0.9.15)
installed
mg
Am Samstag, 5. August 2006 17:54 schrieb Joachim Ansorg:
> Hi,
> several people reported that the CLucene support is broken.
>
> That's true. It is broken, because the file clucene-config.h is in
On Sat, 5 Aug 2006, Joachim Ansorg wrote:
> Hi,
> several people reported that the CLucene support is broken.
I tried to compile Sword for some time ago on Debian unstable. CLucene
had some problem then. Now I tried again (after upgrading Debian) and
compilation worked for some reason, maybe CLuc
Hi,
several people reported that the CLucene support is broken.
That's true. It is broken, because the file clucene-config.h is in
$prefix/lib/CLucene, it can't be found by the other clucene files and break
the compile process.
The fix is to include $prefix/lib/ in the list of include dirs. But
As of clucene 0.9 you can also write a custom sorter, which could
directly compare the verses, thus saving index size - at the cost of a
slower first search (subsequent searches can have their sort cached).
ben
On 12/23/05, DM Smith <[EMAIL PROTECTED]> wrote:
>
> L.J.Arthur Neil wrote:
>
> Hi A
L.J.Arthur Neil wrote:
Hi All,
How can I do soring.I am able to Index and order .But the Sort function doesn't work.
This question may be best answered by the lucene users mailing list.
What are you attempting to do? It is not clear from your example what
you are sorting
Hi All,How can I do soring.I am able to Index and order .But the Sort function doesn't work.I have used the following code; Query* q = QueryParser::parse(tline,_T("contents"),&analyzer); //buf = q->toString(_T("contents")); // _tprintf(_T("Searching for: %s\n\n"), buf)
Sir,
I have installed clucene-0.8.14a version and it works perfectly in the
command line.The problem is,I need the output in browser.I want to use
clucene in my website.Please,suggest me the ways to do that.
(I have also tried by inserting content-type:text/html and compiled like ::
gcc -o se
61 matches
Mail list logo
