[
https://issues.apache.org/jira/browse/LUCENE-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721859#action_12721859
]
Steven Rowe commented on LUCENE-1702:
-------------------------------------
bq. Steven I have been watching that jflex 1.5 branch with great anticipation :)
Cool! If you mention this on the jflex-devel mailing list, you may be able to
help nudge Gerwin Klein (JFlex founder and main developer) into starting work
on merging the 1.5 branch onto the trunk :)
bq. Do you think it will support characters outside of the BMP?
As you may already know, the 1.5 branch does not yet include above-BMP support.
However, this is definitely a future goal.
My guess is that 1.5.0 will be BMP-only, and that 1.5.X or 1.6 will add
above-BMP support. (This is my guess because the Unicode properties code is
present and functional in the branch now, but no work has yet been done to add
above-BMP support.)
> 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: [email protected]
For additional commands, e-mail: [email protected]
