[
https://issues.apache.org/jira/browse/LUCENE-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649125#comment-13649125
]
Christian Moen commented on LUCENE-4956:
----------------------------------------
A quick status update on my side is as follows:
I've put the code into an a module called {{arirang}} on my local setup and
made a few changes necessary to make things work on {{trunk}}.
{{KoreanAnalyzer}} now produces Korean tokens and some tests I've made passes
when run from my IDE.
Loading the dictionaries as resources need some work and I'll spend time on
this during the weekend. I'll also address the headers, etc. to prepare for
the incubator-general vote.
Hopefully, I'll have all this on a branch this weekend. I'll keep you posted
and we can take things from there.
> the korean analyzer that has a korean morphological analyzer and dictionaries
> -----------------------------------------------------------------------------
>
> Key: LUCENE-4956
> URL: https://issues.apache.org/jira/browse/LUCENE-4956
> Project: Lucene - Core
> Issue Type: New Feature
> Components: modules/analysis
> Affects Versions: 4.2
> Reporter: SooMyung Lee
> Labels: newbie
> Attachments: kr.analyzer.4x.tar
>
>
> Korean language has specific characteristic. When developing search service
> with lucene & solr in korean, there are some problems in searching and
> indexing. The korean analyer solved the problems with a korean morphological
> anlyzer. It consists of a korean morphological analyzer, dictionaries, a
> korean tokenizer and a korean filter. The korean anlyzer is made for lucene
> and solr. If you develop a search service with lucene in korean, It is the
> best idea to choose the korean analyzer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
