[
https://issues.apache.org/jira/browse/NUTCH-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514377
]
Doug Cook commented on NUTCH-25:
--------------------------------
I should also add that a significant number of the URLs seem to have been fixed
by the inherent inclusion of Renaud's patch for NUTCH-369 -- this seems very
useful. (Thanks, Renaud!)
Between the charset detection and telling Neko to ignore the specified
character set, things are MUCH better. Here are some good test cases:
http://www.just-drinks.com/blogdetail.aspx?ID=1230
http://www.boissetamerica.com/products/ProductDetails.aspx?PrdId=104
http://www.austincc.edu/bhay/Regionalitaly.doc
http://www.cnr.it/istituti/Istituto_Articoli_conv.html?cds=106&id=18158
http://www.winereviewonline.com/wine_reviews.cfm?nCountryID=2&archives=1
http://www.ngr.ucdavis.edu/varietyview.cfm?varietynum=2942&setdisclaimer=yes
http://www.info.wien.at/article.asp?IDArticle=3811
http://www.iniap.min-agricultura.pt/projectos_detail.aspx?uni=7&id_projecto=872
http://www.finewinepress.com/digital/addfav.php?pid=5&ref=displayimage.php%3Falbum%3Dtopn%26cat%3D0%26pos%3D62
> needs 'character encoding' detector
> -----------------------------------
>
> Key: NUTCH-25
> URL: https://issues.apache.org/jira/browse/NUTCH-25
> Project: Nutch
> Issue Type: Wish
> Reporter: Stefan Groschupf
> Priority: Trivial
> Attachments: NUTCH-25_draft.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: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nutch-developers mailing list
Nutch-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nutch-developers
