[jira] [Commented] (LUCENE-5483) hunspell inaccuracies

2014-07-29 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077830#comment-14077830
 ] 

ASF subversion and git services commented on LUCENE-5483:
-

Commit 1614388 from [~mikemccand] in branch 'dev/trunk'
[ https://svn.apache.org/r1614388 ]

LUCENE-5483: IndexWriter now enforces max docs in one index

 hunspell inaccuracies
 -

 Key: LUCENE-5483
 URL: https://issues.apache.org/jira/browse/LUCENE-5483
 Project: Lucene - Core
  Issue Type: Bug
Reporter: Robert Muir
 Fix For: 4.8, 5.0

 Attachments: LUCENE-5483.patch, LUCENE-5483.patch


 I added a lot of tests and greatly refined this algorithm to match correct 
 hunspell behavior. there were many bugs:
 * recursionLimit was a hack: this is actually specified by the dictionary to 
 be twofold suffix + one prefix, or if COMPLEXPREFIXES is specified, twofold 
 prefix + one suffix. This patch removes cursion limit
 * recursion didn't work correctly: it didnt validate multi-level continuation 
 classes correctly.
 * add COMPLEXPREFIXES support.
 * probably other minor bugs fixed in the process.
 I validated all testing against hunspell



--
This message was sent by Atlassian JIRA
(v6.2#6252)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (LUCENE-5483) hunspell inaccuracies

2014-07-29 Thread Michael McCandless (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14077880#comment-14077880
 ] 

Michael McCandless commented on LUCENE-5483:


Woops, that commit message was meant for LUCENE-5843 instead... I corrected the 
svn log.

 hunspell inaccuracies
 -

 Key: LUCENE-5483
 URL: https://issues.apache.org/jira/browse/LUCENE-5483
 Project: Lucene - Core
  Issue Type: Bug
Reporter: Robert Muir
 Fix For: 4.8, 5.0

 Attachments: LUCENE-5483.patch, LUCENE-5483.patch


 I added a lot of tests and greatly refined this algorithm to match correct 
 hunspell behavior. there were many bugs:
 * recursionLimit was a hack: this is actually specified by the dictionary to 
 be twofold suffix + one prefix, or if COMPLEXPREFIXES is specified, twofold 
 prefix + one suffix. This patch removes cursion limit
 * recursion didn't work correctly: it didnt validate multi-level continuation 
 classes correctly.
 * add COMPLEXPREFIXES support.
 * probably other minor bugs fixed in the process.
 I validated all testing against hunspell



--
This message was sent by Atlassian JIRA
(v6.2#6252)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (LUCENE-5483) hunspell inaccuracies

2014-03-01 Thread Chris Male (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917260#comment-13917260
 ] 

Chris Male commented on LUCENE-5483:


+1

 hunspell inaccuracies
 -

 Key: LUCENE-5483
 URL: https://issues.apache.org/jira/browse/LUCENE-5483
 Project: Lucene - Core
  Issue Type: Bug
Reporter: Robert Muir
 Attachments: LUCENE-5483.patch, LUCENE-5483.patch


 I added a lot of tests and greatly refined this algorithm to match correct 
 hunspell behavior. there were many bugs:
 * recursionLimit was a hack: this is actually specified by the dictionary to 
 be twofold suffix + one prefix, or if COMPLEXPREFIXES is specified, twofold 
 prefix + one suffix. This patch removes cursion limit
 * recursion didn't work correctly: it didnt validate multi-level continuation 
 classes correctly.
 * add COMPLEXPREFIXES support.
 * probably other minor bugs fixed in the process.
 I validated all testing against hunspell



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (LUCENE-5483) hunspell inaccuracies

2014-03-01 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917258#comment-13917258
 ] 

ASF subversion and git services commented on LUCENE-5483:
-

Commit 1573248 from [~rcmuir] in branch 'dev/trunk'
[ https://svn.apache.org/r1573248 ]

LUCENE-5483: fix hunspell inaccuracies

 hunspell inaccuracies
 -

 Key: LUCENE-5483
 URL: https://issues.apache.org/jira/browse/LUCENE-5483
 Project: Lucene - Core
  Issue Type: Bug
Reporter: Robert Muir
 Attachments: LUCENE-5483.patch, LUCENE-5483.patch


 I added a lot of tests and greatly refined this algorithm to match correct 
 hunspell behavior. there were many bugs:
 * recursionLimit was a hack: this is actually specified by the dictionary to 
 be twofold suffix + one prefix, or if COMPLEXPREFIXES is specified, twofold 
 prefix + one suffix. This patch removes cursion limit
 * recursion didn't work correctly: it didnt validate multi-level continuation 
 classes correctly.
 * add COMPLEXPREFIXES support.
 * probably other minor bugs fixed in the process.
 I validated all testing against hunspell



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org



[jira] [Commented] (LUCENE-5483) hunspell inaccuracies

2014-03-01 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/LUCENE-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13917266#comment-13917266
 ] 

ASF subversion and git services commented on LUCENE-5483:
-

Commit 1573251 from [~rcmuir] in branch 'dev/branches/branch_4x'
[ https://svn.apache.org/r1573251 ]

LUCENE-5483: fix hunspell inaccuracies

 hunspell inaccuracies
 -

 Key: LUCENE-5483
 URL: https://issues.apache.org/jira/browse/LUCENE-5483
 Project: Lucene - Core
  Issue Type: Bug
Reporter: Robert Muir
 Fix For: 4.8, 5.0

 Attachments: LUCENE-5483.patch, LUCENE-5483.patch


 I added a lot of tests and greatly refined this algorithm to match correct 
 hunspell behavior. there were many bugs:
 * recursionLimit was a hack: this is actually specified by the dictionary to 
 be twofold suffix + one prefix, or if COMPLEXPREFIXES is specified, twofold 
 prefix + one suffix. This patch removes cursion limit
 * recursion didn't work correctly: it didnt validate multi-level continuation 
 classes correctly.
 * add COMPLEXPREFIXES support.
 * probably other minor bugs fixed in the process.
 I validated all testing against hunspell



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org