[
https://issues.apache.org/jira/browse/LUCENE-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721884#action_12721884
]
Robert Muir commented on LUCENE-1702:
-------------------------------------
Steven, thanks for the information, and the range representation sounds
interesting.
So I'll let others comment if they want it to be fixed pre-1.5.0, in this case
we could define macros in jflex that represent what we want, with comments
indicating how they will be defined in the future jflex.
Either way, a specific unicode version should be selected, with the macros
defined from that unicode version or that unicode version specified to jflex
1.5.0... unicode 5.1 sounds good to me :)
The matchVersion could be used to ensure that back compat always works.
> Thai token type() bug
> ---------------------
>
> Key: LUCENE-1702
> URL: https://issues.apache.org/jira/browse/LUCENE-1702
> Project: Lucene - Java
> Issue Type: Bug
> Components: contrib/analyzers
> Reporter: Robert Muir
> Priority: Minor
>
> While adding tests for offsets & type to ThaiAnalyzer, i discovered it does
> not type Thai numeric digits correctly.
> ThaiAnalyzer uses StandardTokenizer, and this is really an issue with the
> grammar, which adds the entire [:Thai:] block to ALPHANUM.
> i propose that alphanum be described a little bit differently in the grammar.
> Instead, [:letter:] should be allowed to have diacritics/signs/combining
> marks attached to it.
> this would allow the [:thai:] hack to be completely removed, would allow
> StandardTokenizer to parse complex writing systems such as Indian languages,
> and would fix LUCENE-1545.
--
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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
