lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Moen (Commented) (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3921) Add decompose compound Japanese Katakana token capability to Kuromoji
Date Mon, 26 Mar 2012 10:28:28 GMT


Christian Moen commented on LUCENE-3921:

Hello, Kazu.  Long time no see -- I hope things are well!

This is very good feature request.  I think this is possible by changing how we emit unknown
words, i.e. by not emitting them as greedily and giving the lattice more segmentation options.
 For example, if we find an unknown word トートバッグ (by regular greedy matching),
we can emit


in the current position.  When we reach the position that starts with バッグ, we'll find
a known word, and when the Viterbi runs, it's likely to choose トート and バッグ as
the best path.

Let me have a look at this by looking into the lattice details.
> Add decompose compound Japanese Katakana token capability to Kuromoji
> ---------------------------------------------------------------------
>                 Key: LUCENE-3921
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: modules/analysis
>    Affects Versions: 4.0
>         Environment: Cent OS 5, IPA Dictionary, Run with "Search mdoe"
>            Reporter: Kazuaki Hiraga
>              Labels: features
> Japanese morphological analyzer, Kuromoji doesn't have a capability to decompose every
Japanese Katakana compound tokens to sub-tokens. It seems that some Katakana tokens can be
decomposed, but it cannot be applied every Katakana compound tokens. For instance, "トートバッグ(tote
bag)" and "ショルダーバッグ" don't decompose into "トート バッグ" and "ショルダー
バッグ" although the IPA dictionary has "バッグ" in its entry.  I would like to apply
the decompose feature to every Katakana tokens if the sub-tokens are in the dictionary or
add the capability to force apply the decompose feature to every Katakana tokens.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message