[LUCENE-1373] Most of the contributed Analyzers suffer from invalid recognition of acronyms.

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 2.3.2
• Component/s: modules/analysis
• Lucene Fields: New
• Assignee: Unassigned
• Reporter: Mark Lassau
• Created: 03/Sep/08 00:56
• Updated: 16/May/11 18:15
• Resolved: 22/Oct/09 19:54

Description

LUCENE-1068 describes a bug in StandardTokenizer whereby a string like "www.apache.org." would be incorrectly tokenized as an acronym (note the dot at the end).

Unfortunately, keeping the "backward compatibility" of a bug turns out to harm us.
StandardTokenizer has a couple of ways to indicate "fix this bug", but unfortunately the default behaviour is still to be buggy.
Most of the non-English analyzers provided in lucene-analyzers utilize the StandardTokenizer, and in v2.3.2 not one of these provides a way to get the non-buggy behaviour

I refer to:

• BrazilianAnalyzer
• CzechAnalyzer
• DutchAnalyzer
• FrenchAnalyzer
• GermanAnalyzer
• GreekAnalyzer
• ThaiAnalyzer

Issue Links

• is part of: LUCENE-2002 Add oal.util.Version ctor to QueryParser
• relates to: LUCENE-1403 StandardTokenizer - Improper Hostname Recognition
• relates to: LUCENE-1068 Invalid behavior of StandardTokenizerImpl
• relates to: LUCENE-1151 Fix StandardAnalyzer to not mis-identify HOST as ACRONYM by default