lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Moen (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LUCENE-3909) Move Kuromoji to analysis.ja and introduce Japanese* naming
Date Mon, 26 Mar 2012 17:50:33 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-3909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Christian Moen resolved LUCENE-3909.
------------------------------------

    Resolution: Fixed
    
> Move Kuromoji to analysis.ja and introduce Japanese* naming
> -----------------------------------------------------------
>
>                 Key: LUCENE-3909
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3909
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: modules/analysis
>    Affects Versions: 3.6, 4.0
>            Reporter: Christian Moen
>            Assignee: Christian Moen
>
> Lucene/Solr 3.6 and 4.0 will get out-of-the-box Japanese language support through {{KuromojiAnalyzer}},
{{KuromojiTokenizer}} and various other filters.  These filters currently live in {{org.apache.lucene.analysis.kuromoji}}.
> I'm proposing that we move Kuromoji to a new Japanese package {{org.apache.lucene.analysis.ja}}
in line with how other languages are organized.  As part of this, I also think we should rename
{{KuromojiAnalyzer}} to {{JapaneseAnalyzer}}, etc. to further align naming to our conventions
by making it very clear that these analyzers are for Japanese.  (As much as I like the name
"Kuromoji", I think "Japanese" is more fitting.)
> A potential issue I see with this that I'd like to raise and get feedback on, is that
end-users in Japan and elsewhere who use lucene-gosen could have issues after an upgrade since
lucene-gosen is in fact releasing its analyzers under the {{org.apache.lucene.analysis.ja}}
namespace (and we'd have a name clash).
> I believe users should have the freedom to choose whichever Japanese analyzer, filter,
etc. they'd like to use, and I don't want to propose a name change that just creates unnecessary
problems for users, but I think the naming proposed above is most fitting for a Lucene/Solr
release.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


Mime
View raw message