<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">We'll try to get to Lucene 3.6.2 for the release if at all possible. To go to Lucene 4.x requires Java 6.<div><br></div><div>Regarding Java 6: The hold up is Mac OSX. The first availability of it is to those with a 64-bit Intel processor running Leopard (10.5). It is not installed by default and when installed requires the user to set a preference in order to be able to use it. (Not something mac users are inclined to do.) So the first Mac OS where we can reasonably expect users to have Java 6 is Snow Leopard.</div><div><br></div><div>BTW, I have a Mac of this vintage that's running just fine. It originally it had a 32-bit dual core, which I upgraded to a 64-bit processor. Just to get Java 6 under Leopard.</div><div><br></div><div>Anyway, after this release we can reconsider Java 6. We'll create a maintenance branch for the release to be able to do bug fixes.</div><div><br></div><div>-- DM<br><div><br></div><div><br></div><div><br><div><div>On Feb 12, 2013, at 1:01 PM, DM Smith <<a href="mailto:dmsmith@crosswire.org">dmsmith@crosswire.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">It is a lot of work. The analyzers and filters that we have written would need to be re-written. The code no longer uses String but rather char[] (or equivalent).<div><br></div><div>This happened well before 4.0. Typically w/ Lucene you don't want to directly upgrade from an early version of a prior release but only from the x.9 release. The difference between 3.9 and earlier is that lots of stuff is deprecated. The difference between 3.9 and 4.0 is that the deprecations are gone.</div><div><br></div><div>This has been very helpful in identifying how to go from one major release to the next.</div><div><br></div><div>We have custom language converters because theirs do too much. For example, they remove stop words. While this is generally nice. There are theological phrases in which stop words are significant, e.g. "in Christ"</div><div><br></div><div>Also most are built on StandardAnalyzer, which is slow and it's features are not appropriate. We use a very simple analyzer from Lucene.</div><div><br></div><div>There are some new Filters and Analyzers that we should be using.</div><div><br></div><div>I'd like to do this before we release or shortly after.</div><div><br></div><div>BTW, I want to get back to a release often practice.</div><div><br></div><div>In Him,</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>DM</div><div><br><div><div>On Feb 12, 2013, at 10:15 AM, Chris Burrell <<a href="mailto:chris@burrell.me.uk">chris@burrell.me.uk</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">So on the JSword front, it would be good to move up to Lucene 4 at some stage. Are we saying this will need more work than just a simple upgrade?<div><br></div><div>Also, why do we have our custom language converters. Lucene seems to have most of the ones we're using, and we seem to simply wrap around the Filters in the library?</div>
<div><br></div><div style="">Chris</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 12 February 2013 15:12, DM Smith <span dir="ltr"><<a href="mailto:dmsmith@crosswire.org" target="_blank">dmsmith@crosswire.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Reposting to JSword-devel.<br>
<div><div class="h5"><br>
On Feb 12, 2013, at 6:47 AM, David Haslam wrote:<br>
<br>
> Some languages, like Japanese and Chinese, are configured in JSword to use<br>
> the SmartCN Lucene Analyzer.<br>
><br>
> SmartCN contains a massive dictionary which is too large for most mobiles.<br>
><br>
> We don't package SmartCN with And Bible so somebody needs to do some work to<br>
> find a replacement Lucene Analyzer for Japanese.<br>
><br>
> cf. For Chinese we now use mmseg4j.<br>
><br>
> David (on behalf of Martin)<br>
><br>
> <a href="https://code.google.com/p/and-bible/issues/detail?id=160" target="_blank">https://code.google.com/p/and-bible/issues/detail?id=160</a><br>
><br>
><br>
><br>
> --<br>
> View this message in context: <a href="http://sword-dev.350566.n4.nabble.com/Replacement-Lucene-Analyzer-for-Japanese-tp4651942.html" target="_blank">http://sword-dev.350566.n4.nabble.com/Replacement-Lucene-Analyzer-for-Japanese-tp4651942.html</a><br>
> Sent from the SWORD Dev mailing list archive at <a href="http://nabble.com/">Nabble.com</a>.<br>
><br>
> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
<br>
<br>
</div></div>_______________________________________________<br>
jsword-devel mailing list<br>
<a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/jsword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
</blockquote></div><br></div>
_______________________________________________<br>jsword-devel mailing list<br><a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br><a href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br></blockquote></div><br></div></div>_______________________________________________<br>jsword-devel mailing list<br><a href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>http://www.crosswire.org/mailman/listinfo/jsword-devel<br></blockquote></div><br></div></div></body></html>