[ https://issues.apache.org/jira/browse/LUCENE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563548#action_12563548 ]
Grant Ingersoll commented on LUCENE-1151: ----------------------------------------- Not necessarily related, but can you think of a way that we can keep WikipediaTokenizer and StandardTokenizer in sync for these kind of things. I guess I need to go look in JFlex to see if there is a way to do inheritance. Essentially, I want the WikiTokenizer to be StandardTokenizer plus handle the Wiki syntax appropriately. > Fix StandardAnalyzer to not mis-identify HOST as ACRONYM by default > ------------------------------------------------------------------- > > Key: LUCENE-1151 > URL: https://issues.apache.org/jira/browse/LUCENE-1151 > Project: Lucene - Java > Issue Type: Improvement > Components: Analysis > Reporter: Michael McCandless > Assignee: Michael McCandless > Priority: Minor > Fix For: 2.4 > > Attachments: LUCENE-1151.patch > > > Coming out of the discussion around back compatibility, it seems best to > default StandardAnalyzer to properly fix LUCENE-1068, while preserving the > ability to get the back-compatible behavior in the rare event that it's > desired. > This just means changing the replaceInvalidAcronym = false with = true, and, > adding a clear entry to CHANGES.txt that this very slight non back compatible > change took place. > Spinoff from here: > http://www.gossamer-threads.com/lists/lucene/java-dev/57517#57517 > I'll commit that change in a day or two. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]