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

Steve Rowe commented on LUCENE-4956:
------------------------------------

Jack, I think documentation can address most of your concerns.  See e.g. the 
descriptions for the analyzer packages in the API javadocs section of the 
top-level per-release docs: [http://lucene.apache.org/core/4_2_1/index.html].  
Fortunately, a module's name is not the only opportunity to describe its 
functionality.

bq. Even if you just called the module "korean", at least that would be a 
helpful guide to people like me browsing the list of modules. and then the 
package name can distinguish the implementations for that language.

-1.  The stempel and morfologik analysis modules are both Polish analyzers - if 
the first one had been named "polish", what would we have done with the second 
one?

bq. Also, it should be possible to mix multiple implementations for the same 
langauge in the same application, so, the package name does not to have some 
unique name, unless there is guaranteed to be only one implementation for that 
language.

I agree that mixing same-language implementations should be possible in the 
same application.  I have no idea what you're saying after that.  Maybe an 
example?


                
> 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]

Reply via email to