[
https://issues.apache.org/jira/browse/NUTCH-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12515461
]
Doug Cook commented on NUTCH-25:
--------------------------------
> Can you provide a link on icu4j's language detection?
http://www.icu-project.org/apiref/icu4j/
It's still part of CharsetDetector. The CharsetMatch object(s) returned by
detect() or detectAll() provide a getLanguage() method. I was wondering why my
return set had a number of different CharsetMatch objects returned, all with
the same encoding guess, all with different confidences; then I realized it's
because these are guesses for different languages. For example, for a page in
german, you might see:
2007-07-25 15:16:16,536 DEBUG parse.EncodingDetector
(EncodingDetector.java:autoDetectClues(204)) - enc=windows-1252,de (81%
confidence)
2007-07-25 15:16:16,542 DEBUG parse.EncodingDetector
(EncodingDetector.java:autoDetectClues(204)) - enc=windows-1252,nl (50%
confidence)
2007-07-25 15:16:16,544 DEBUG parse.EncodingDetector
(EncodingDetector.java:autoDetectClues(204)) - enc=windows-1252,da (41%
confidence)
2007-07-25 15:16:16,544 DEBUG parse.EncodingDetector
(EncodingDetector.java:autoDetectClues(204)) - enc=windows-1252,fr (38%
confidence)
(etc)
I'm not sure how good the guesses are, but for the few examples I looked at, it
was spot on.
Still thinking about all the other stuff-
d
> needs 'character encoding' detector
> -----------------------------------
>
> Key: NUTCH-25
> URL: https://issues.apache.org/jira/browse/NUTCH-25
> Project: Nutch
> Issue Type: New Feature
> Reporter: Stefan Groschupf
> Assignee: Doğacan Güney
> Fix For: 1.0.0
>
> Attachments: EncodingDetector.java, NUTCH-25.patch,
> NUTCH-25_draft.patch, patch
>
>
> transferred from:
> http://sourceforge.net/tracker/index.php?func=detail&aid=995730&group_id=59548&atid=491356
> submitted by:
> Jungshik Shin
> this is a follow-up to bug 993380 (figure out 'charset'
> from the meta tag).
> Although we can cover a lot of ground using the 'C-T'
> header field in in the HTTP header and the
> corresponding meta tag in html documents (and in case
> of XML, we have to use a similar but a different
> 'parsing'), in the wild, there are a lot of documents
> without any information about the character encoding
> used. Browsers like Mozilla and search engines like
> Google use character encoding detectors to deal with
> these 'unlabelled' documents.
> Mozilla's character encoding detector is GPL/MPL'd and
> we might be able to port it to Java. Unfortunately,
> it's not fool-proof. However, along with some other
> heuristic used by Mozilla and elsewhere, it'll be
> possible to achieve a high rate of the detection.
> The following page has links to some other related pages.
> http://trainedmonkey.com/week/2004/26
> In addition to the character encoding detection, we
> also need to detect the language of a document, which
> is even harder and should be a separate bug (although
> it's related).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Nutch-developers mailing list
Nutch-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nutch-developers
