[ 
https://issues.apache.org/jira/browse/LUCENE-4956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796545#comment-13796545
 ] 

Christian Moen commented on LUCENE-4956:
----------------------------------------

SooMyung, I've committed the latest changes we merged in Seoul on Monday.  It's 
great if you can fix the decompounding issue we came across, which we disabled 
a test for.

Uwe, +1 to use {{Class#getResourceAsStream}} and remove {{FileUtils}} and 
{{JarResources}}.  I'll make these changes and commit to the branch.

Overall, I think there's a lot of things we can do to improve this code.  Would 
very much like to hear your opinion on what we should fix before committing to 
trunk and getting this on the 4.x branch and improve from there.  My thinking 
is that it might be good to get this committed so we'll have Korean working 
even though the code needs some work.  SooMyung has a community in Korea that 
uses and it's serving their needs as far as I understand.

Happy to hear people's opinion on this.

> 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
>            Assignee: Christian Moen
>              Labels: newbie
>         Attachments: kr.analyzer.4x.tar, lucene-4956.patch, lucene4956.patch, 
> LUCENE-4956.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to