Re: [sword-devel] PocketSword beta testing

Hi, So, yesterday I took a look at Nic’s new code and compared it to the last code that I had worked on which turned out to be back in Dec. It seems that a lot of our code may be complimentary to each other! :) So, this is good news. I need to dig in some more, but it looks like we foc

[sword-devel] luke - the toolkit for lucene

DM pointed us to https://code.google.com/archive/p/luke/ FIO. There are also one or two forks of *luke* on GitHub. I'd be out of my depth in this stuff. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/luke-the-toolkit-for-lucene-tp4657117.html Sent from the SWO

Re: [sword-devel] Lucene search index and Coptic ?

FIO. Zip contains the .conf file that I updated yesterday. sahidicbible.zip btw. I just missed out the "upload file" step before. David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Lucene-sea

Re: [sword-devel] Lucene search index and Coptic ?

Yes - of course! Encoding=UTF-8 It's not primarily a font issue, even though that might be a further annoyance in Xiphos. Having a font without coverage for the Coptic block in question cannot by any stretch of logic account for a search that finds 622,900% of the only 2 true matches. A font ca

Re: [sword-devel] Lucene search index and Coptic ?

Has anyone checked the encoding entry in the conf file? On April 27, 2017 6:57:48 AM MST, Greg Hellings wrote: >On Thu, Apr 27, 2017 at 3:59 AM, David Haslam >wrote: > >> Even if Troy's good friends don't use the Lucene index for their work >on >> Coptic manuscripts, that's no reason not to purs

Re: [sword-devel] Lucene search index and Coptic ?

On Thu, Apr 27, 2017 at 3:59 AM, David Haslam wrote: > Even if Troy's good friends don't use the Lucene index for their work on > Coptic manuscripts, that's no reason not to pursue this issue in more > detail. > > The *Coptic* block *2C80..2CFF* was added with *Unicode 4.1* which was > released i

Re: [sword-devel] Lucene search index and Coptic ?

No - I've not tried any command line utilities related to Lucene search. Were you thinking of *diatheke*? If it is a font issue, it's not as if I hadn't already installed the recommended *Antinoou* font for the SahidicBible module and selected this font in Xiphos. http://www.evertype.com/fonts/c

Re: [sword-devel] Lucene search index and Coptic ?

Hi DM, I wouldn't know where to begin with *Luke*; there's no documentation for it in the code archive you cited. Is it even something a Windows user like me could do anything with? Best regards, David -- View this message in context: http://sword-dev.350566.n4.nabble.com/Lucene-search-inde

Re: [sword-devel] Lucene search index and Coptic ?

Even if Troy's good friends don't use the Lucene index for their work on Coptic manuscripts, that's no reason not to pursue this issue in more detail. The *Coptic* block *2C80..2CFF* was added with *Unicode 4.1* which was released in March 2005. Are we concluding that the Lucene indexing software