Re: [sword-devel] CLucene 2

2011-10-04 Thread Troy A. Griffitts
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

Re: [sword-devel] CLucene 2

2011-10-03 Thread Deji Akingunola
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

Re: [sword-devel] CLucene 2

2011-09-02 Thread Matthew Talbert
> 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

Re: [sword-devel] CLucene 2

2011-09-02 Thread Greg Hellings
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

Re: [sword-devel] CLucene 2

2011-09-02 Thread Matthew Talbert
> 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

Re: [sword-devel] CLucene 2

2011-09-02 Thread DM Smith
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

[sword-devel] CLucene 2

2011-09-02 Thread Greg Hellings
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