[ 
https://issues.apache.org/jira/browse/NUTCH-1397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295732#comment-13295732
 ] 

Lewis John McGibbney edited comment on NUTCH-1397 at 6/15/12 3:52 PM:
----------------------------------------------------------------------

Hi Ken, this is exactly what flashed through my mind when i opened the ticket. 
I hoped that one of you Tika guys would chime in and provide some commentary. 
Right enough language-identification IS delegated to Tika since NUTCH-1075 so 
yes I think your right. I'll check on the Tika Jira, if one doesn't exist then 
I will open accordingly. Thanks.
                
      was (Author: lewismc):
    Hi KEN, this is exactly what flashed through my mind when i opened the 
ticket. I hoped that one of you Tika guys would chime in and provide some 
commentary. Right enough language-identification IS delegated to Tika since 
NUTCH-1075 so yes I think your right. I'll check on the Tika Jira, if one 
doesn't exist then I will open accordingly. Thanks.
                  
> language-identifier incorrectly handles double-barreled language properties
> ---------------------------------------------------------------------------
>
>                 Key: NUTCH-1397
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1397
>             Project: Nutch
>          Issue Type: Improvement
>          Components: parser
>    Affects Versions: nutchgora, 1.5
>            Reporter: Lewis John McGibbney
>            Priority: Minor
>             Fix For: 1.6, 2.1
>
>
> Currently when language-identifier is activated is parses and identifies 
> langauge-type=en, however does not identify en-GB or en-US. This issues 
> should correct that. 

--
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

        

Reply via email to