tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joseph Vychtrle (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-369) Improve accuracy of language detection
Date Fri, 04 Nov 2011 01:47:32 GMT

    [ https://issues.apache.org/jira/browse/TIKA-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13143676#comment-13143676

Joseph Vychtrle commented on TIKA-369:

Wouldn't it be better if the field wasn't private and developers could set it up according
to the situation ?
> Improve accuracy of language detection
> --------------------------------------
>                 Key: TIKA-369
>                 URL: https://issues.apache.org/jira/browse/TIKA-369
>             Project: Tika
>          Issue Type: Improvement
>          Components: languageidentifier
>    Affects Versions: 0.6
>            Reporter: Ken Krugler
>            Assignee: Ken Krugler
>         Attachments: Surprise and Coincidence.pdf, lingdet-mccs.pdf, textcat.pdf
> Currently the LanguageProfile code uses 3-grams to find the best language profile using
Pearson's chi-square test. This has three issues:
> 1. The results aren't very good for short runs of text. Ted Dunning's paper (attached)
indicates that a log-likelihood ratio (LLR) test works much better, which would then make
language detection faster due to less text needing to be processed.
> 2. The current LanguageIdentifier.isReasonablyCertain() method uses an exact value as
a threshold for certainty. This is very sensitive to the amount of text being processed, and
thus gives false negative results for short runs of text.
> 3. Certainty should also be based on how much better the result is for language X, compared
to the next best language. If two languages both had identical sum-of-squares values, and
this value was below the threshold, then the result is still not very certain.

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


View raw message