[
https://issues.apache.org/jira/browse/LUCENE-1702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721867#action_12721867
]
Robert Muir commented on LUCENE-1702:
-------------------------------------
Steven, even without >BMP support, 1.5 branch would make the grammar file more
clear and maintainable.
Otherwise, codepoint ranges must be used.
I'll take your advice and send the nudge.
I think for this issue it would be best to wait for the 1.5.0 version of jflex
for clarity.
I think even without >BMP support, we should be able to still function.
ex: surrogate pairs with lead surrogate D840-D87F point to the SIP, so they
should be typed as CJK.
for reference (haven't looked at jflex), above-bmp support might require new
data structures. I think ICU uses things like tries / compactarrays to deal
with the fact you have thousands of codepoints with the same property value,
etc.
> 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]
